From: Greg Troxel <gdt@work.lexort.com>
To: ding@gnus.org
Subject: reply-to and lists - a hard case
Date: Thu, 05 Jul 2012 14:19:53 -0400 [thread overview]
Message-ID: <smutxxm83zq.fsf@linuxpal.mit.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 814 bytes --]
I subscribe to source-changes@netbsd.org and got a message like this:
From: "Fred" <fred_redacted@netbsd.org>
Subject: CVS commit: src/sys/arch/powerpc/booke
To: source-changes@NetBSD.org
Date: Thu, 5 Jul 2012 17:25:36 +0000 (50 minutes, 55 seconds ago)
Reply-To: source-changes-d@NetBSD.org
Mail-Followup-To: source-changes-d@NetBSD.org
I hit 'f' and asked a question about the change. gnus composed a mail
which was To: fred and CC: source-changes.
I do have broken-reply-to set on some lists, but this is a funny case;
the intent is to have replies that do go to the list go to a discuss
list, not to force people not to send private replies.
So I'm curious what the collective gnus wisdom is here.
(emacs 23, gnus fairly recent git head)
[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]
next reply other threads:[~2012-07-05 18:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 18:19 Greg Troxel [this message]
2012-07-06 12:28 ` Julien Danjou
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=smutxxm83zq.fsf@linuxpal.mit.edu \
--to=gdt@work.lexort.com \
--cc=ding@gnus.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).