From: Andrew Pimlott <andrew@pimlott.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: [sup-talk] Reply-To: not offered as reply recipient
Date: Fri, 15 Oct 2010 09:01:49 -0700 [thread overview]
Message-ID: <1287156818-sup-6475@pimlott.net> (raw)
Just a ping: there was this thread on what reply recipients to offer in
some mailing list cases:
http://www.mail-archive.com/sup-talk@rubyforge.org/msg02206.html
Replying to list admin messages is still pretty broken. They set
Reply-To to a magic address, but sup does not offer it as an option
because of the mailing list headers. Really annoying. Any further
thoughts on resolving this?
Andrew
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
reply other threads:[~2010-10-15 16:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1287156818-sup-6475@pimlott.net \
--to=andrew@pimlott.net \
--cc=sup-talk@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox