Gnus development mailing list
 help / color / mirror / Atom feed
From: larsi@ifi.uio.no (Lars Magne Ingebrigtsen)
Subject: Re: Mailing to several people.
Date: 01 Dec 1995 04:57:41 +0100	[thread overview]
Message-ID: <w8spwe9cu6i.fsf@surt.ifi.uio.no> (raw)
In-Reply-To: "Steven L. Baur"'s message of Wed, 29 Nov 1995 12:32:45 -0800

"Steven L. Baur" <steve@miranova.com> writes:

> 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.

I think this breaks all just about all RFCs ever written, which is a
plus.  :-)  

Actually, it doesn't break RFC822, which doesn't specify anything
about the References header except that it should "refer" to the mails
you reply to, so it would be ok.  However, I don't think any other
mail agent does anything like this, and there are practical
ramifications that I'd rather not think too much about.

Uhmn, I just don't know.  I'm leaning towards dropping the References
line completely and creating a Subject line without any "Re: ", with
all the different subjects separated by a " / ".  So one would start a
new thread by replying to several mails at once.

This won't break anything, but, on the other hand, it might not be
what one would want...

Either that, or just use the References from one of the messages --
the first, for instance.

-- 
Home is where the cat is.


      parent reply	other threads:[~1995-12-01  3:57 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
1995-11-30  8:19       ` Felix Lee
1995-12-01  3:57       ` Lars Magne Ingebrigtsen [this message]

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=w8spwe9cu6i.fsf@surt.ifi.uio.no \
    --to=larsi@ifi.uio.no \
    /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).