From: Wes Hardaker <wes@hardakers.net>
Cc: ding@gnus.org
Subject: Re: references on multiple message followup
Date: Tue, 19 Feb 2002 22:04:53 -0800 [thread overview]
Message-ID: <sd664s4rju.fsf@wanderer.hardakers.net> (raw)
In-Reply-To: <87lmdpj92f.fsf@zip.com.au> (Kevin Ryde's message of "Wed, 20 Feb 2002 10:22:48 +1000")
>>>>> On Wed, 20 Feb 2002 10:22:48 +1000, Kevin Ryde <user42@zip.com.au> said:
Kevin> If I process mark a couple of articles to followup, so as to
Kevin> quote all the text, the references constructed seems to be
Kevin> based only on the first article.
As long as I'm at it, doing followups of multiple articles no longer
includes a merged copy of the to/cc lists and just takes the first or
last one (I forget) (no I don't. I just tried it again, it takes the
first address list one only, but quotes text from them all).
--
"Ninjas aren't dangerous. They're more afraid of you than you are of them."
next prev parent reply other threads:[~2002-02-20 6:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-20 0:22 Kevin Ryde
2002-02-20 1:27 ` Karl Kleinpaste
2002-02-20 1:27 ` Karl Kleinpaste
2002-02-22 0:26 ` Kevin Ryde
2002-02-22 0:26 ` Kevin Ryde
2002-02-20 6:04 ` Wes Hardaker [this message]
2002-02-20 6:04 ` Wes Hardaker
2002-02-20 0:22 Kevin Ryde
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=sd664s4rju.fsf@wanderer.hardakers.net \
--to=wes@hardakers.net \
--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).