From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Process mark and follow up/reply
Date: Mon, 30 Aug 2010 08:36:39 -0500 [thread overview]
Message-ID: <87y6bop6hk.fsf@lifelogs.com> (raw)
In-Reply-To: <m3iq2u1k9q.fsf@quimbies.gnus.org>
On Sat, 28 Aug 2010 23:48:17 +0200 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
LMI> asjo@koldfront.dk (Adam Sjøgren) writes:
>> This opened a buffer with the four emails quoted, as expected, but the
>> To: header only contained the sender (/Reply-To) from the _first_ email,
>> and not, as I expected, the senders of _all_ the marked emails.
LMI> That's the documented behaviour, I think. It might make more sense to
LMI> include all the To/Cc headers from all the articles... Hm. I can't
LMI> really see any instances where it wouldn't make sense, but I have a
LMI> feeling this was discussed before...
I don't recall the discussion; I'm in favor of using all the names as
Adam suggested.
Ted
next prev parent reply other threads:[~2010-08-30 13:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-24 17:45 Adam Sjøgren
2010-08-28 21:48 ` Lars Magne Ingebrigtsen
2010-08-30 13:36 ` Ted Zlatanov [this message]
2010-08-30 18:06 ` Lars Magne Ingebrigtsen
2010-08-31 18:40 ` Ted Zlatanov
2010-08-31 18:47 ` Lars Magne Ingebrigtsen
2010-08-31 18:56 ` Ted Zlatanov
2010-08-31 21:08 ` Adam Sjøgren
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=87y6bop6hk.fsf@lifelogs.com \
--to=tzz@lifelogs.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).