From: "Steven L. Baur" <steve@miranova.com>
Subject: Re: Mailing to several people.
Date: Wed, 29 Nov 1995 12:32:45 -0800 [thread overview]
Message-ID: <199511292032.MAA12792@miranova.com> (raw)
In-Reply-To: <w8s7n0jxq4e.fsf@gymir.ifi.uio.no>
>>>>> "Lars" == Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:
Lars> After fixing a couple of bugs, this is what happens in
Lars> September 0.17:
Lars> 1) A mail reply buffer is set up the normal way based on the
Lars> first process marked article.
Lars> 2) All subsequent articles are yanked with citation lines
Lars> (hopefully) now inserted where they should be. (This didn't
Lars> work in 0.16.)
Lars> That's yucky. But it's not self-evident what should happen
Lars> here.
Lars> I think all From, To and Cc lines from the articles should
Lars> be catenated as if replying to a single article that had
Lars> quite long From, To and Cc lines:
Lars> Article A:
Lars> From: larsi Cc: ding To: per
Lars> Article B:
Lars> From: gnus-bug Cc: Steve
Lars> =>
Lars> From: larsi, gnus-bug Cc: ding, Steve To: Per
Lars> And then Gnus uses the normal methods to find out what
Lars> headers it should put in the reply mail.
Lars> What about References, In-Reply-To and Subject, though?
All existing references should be catenated. Add all the collected
message-ids to them. Since this ties previously unconnected threads
together it will make for some interesting later threading decisions.
In-Reply-To, take the first article collected.
Subject, take the subject from the first article collected. You could
perhaps add a configurable string to it like ``, etc.'' or ``-reply'' :-).
--
steve@miranova.com baur
next prev parent reply other threads:[~1995-11-29 20:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-11-24 11:33 Andy Eskilsson
1995-11-24 19:57 ` Steven L. Baur
1995-11-29 17:55 ` Lars Magne Ingebrigtsen
1995-11-29 19:27 ` Edward J. Sabol
1995-11-29 20:36 ` Steven L. Baur
1995-11-29 20:32 ` Steven L. Baur [this message]
1995-11-30 8:19 ` Felix Lee
1995-12-01 3:57 ` Lars Magne Ingebrigtsen
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=199511292032.MAA12792@miranova.com \
--to=steve@miranova.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 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).