Gnus development mailing list
 help / color / mirror / Atom feed
From: Wes Hardaker <Wesley.Hardaker@sphys.unil.ch>
Cc: ding@ifi.uio.no
Subject: Re: [Announce] Mine game v1.17 for Emacs
Date: 31 Jan 1997 11:23:55 +0100	[thread overview]
Message-ID: <qk2bua6dtxg.fsf@iptsun2.unil.ch> (raw)
In-Reply-To: Richard Stallman's message of Fri, 31 Jan 1997 04:36:21 -0500

>>>>> "RS" == Richard Stallman <rms@gnu.ai.mit.edu> writes:

RS> Is it desirable to make both an In-reply-to and a References
RS> referring to the same message?

Yes, I believe so...  Well...  actually I'm not possitive.  I'd ask
Lars or read the RFCs to be sure.  I doubt it would hurt.  The
references header is better (more information) than the in-reply-to
and I don't know if there is any mailer that uses it in the first
place.  I doubt it actually...  Gnus will recognize it, but uses
references instead if found.  I suspect that all mailers that even
look at the in-reply-to header will also look for the references
header and use it instead.  

Well, in short, no...  I don't think you *have* to do both.
Desirable, who knows...

Heck, I'm cc'ing this to the ding list because thats where more
experts lie (ie, Lars???).  They should be able to answer better.

Wes


       reply	other threads:[~1997-01-31 10:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <qk2n2tqe1f2.fsf@iptsun2.unil.ch>
     [not found] ` <199701310720.CAA00587@psilocin.gnu.ai.mit.edu>
     [not found]   ` <199701310936.EAA01473@psilocin.gnu.ai.mit.edu>
1997-01-31 10:23     ` Wes Hardaker [this message]
1997-01-31 11:25       ` Per Abrahamsen
1997-01-31 11:33       ` Per Persson
1997-01-31 15:54       ` Lantz Moore
1997-01-31 22:23       ` Lars Magne Ingebrigtsen
1997-02-03  8:07         ` Wes Hardaker
1997-02-03 16:16           ` 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=qk2bua6dtxg.fsf@iptsun2.unil.ch \
    --to=wesley.hardaker@sphys.unil.ch \
    --cc=ding@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).