From: Phillip Susi <psusi@cfl.rr.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Reply-to munging
Date: Tue, 19 Jun 2007 18:02:49 -0400 [thread overview]
Message-ID: <46785289.6010602@cfl.rr.com> (raw)
Please change the list to stop munging reply-to headers. See this for a
slew of reasons why it is bad:
http://www.unicom.com/pw/reply-to-harmful.html
The most annoying to me are that it breaks my ability to reply to the
original poster off list when I feel it is appropriate, and to properly
reply to threads which are cross posted to more than one list.
next reply other threads:[~2007-06-19 22:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-19 22:02 Phillip Susi [this message]
2007-06-20 14:44 ` Reply-to munging Alasdair G Kergon
2007-07-02 19:55 ` Phillip Susi
2007-07-02 20:48 ` Alasdair G Kergon
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=46785289.6010602@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=dm-devel@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.