From: Jan Kiszka <jan.kiszka@web.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [RFC] remove enforced 'reply-to' for mailing list
Date: Mon, 18 Aug 2008 20:39:54 +0200 [thread overview]
Message-ID: <48A9C1FA.5060800@web.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 520 bytes --]
Hi,
some posters already ignore this hard-coded, rather untypical policy,
other don't, and the result is sometimes fairly chaotic:
Can we remove the 'reply-to' that is injected into every list posting?
IMHO, it complicates things because carefully built up CC lists easily
get lost this way unless you are replying to a mail you received
directly. Mailman should have an option to avoid duplicate deliveries in
case you are subscribed and on CC. Or is there any other reason for this
'reply-to'?
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
reply other threads:[~2008-08-18 18:41 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=48A9C1FA.5060800@web.de \
--to=jan.kiszka@web.de \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).