From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Cc: Richard Stallman <rms@gnu.ai.mit.edu>
Subject: Re: [Announce] Mine game v1.17 for Emacs
Date: 31 Jan 1997 23:23:38 +0100 [thread overview]
Message-ID: <m29159bi1h.fsf@proletcult.slip.ifi.uio.no> (raw)
In-Reply-To: Wes Hardaker's message of 31 Jan 1997 11:23:55 +0100
Wes Hardaker <Wesley.Hardaker@sphys.unil.ch> writes:
> >>>>> "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 has a strictly defined syntax (defined by
RFC1036 for news, but is used by most mail agents as well) and is
therefore usable for building threads. There is no syntax
specification of the In-Reply-To header.
Here are the two headers from Wes' article:
References: <qk2n2tqe1f2.fsf@iptsun2.unil.ch>,
<199701310720.CAA00587@psilocin.gnu.ai.mit.edu> <199701310936.EAA01473@psilocin.gnu.ai.mit.edu>
In-Reply-To: Richard Stallman's message of Fri, 31 Jan 1997 04:36:21 -0500
(The References header is malformed, by the way -- there should be no
comma after the first Message-ID.)
Having the References header is vital, while the In-Reply-To header
carries some informal information which might be nice to have.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@ifi.uio.no * Lars Ingebrigtsen
next prev parent reply other threads:[~1997-01-31 22: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
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 [this message]
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=m29159bi1h.fsf@proletcult.slip.ifi.uio.no \
--to=larsi@ifi.uio.no \
--cc=rms@gnu.ai.mit.edu \
/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).