From: Per Abrahamsen <abraham@dina.kvl.dk>
Cc: Richard Stallman <rms@gnu.ai.mit.edu>
Subject: Re: [Announce] Mine game v1.17 for Emacs
Date: 31 Jan 1997 12:25:45 +0100 [thread overview]
Message-ID: <rjlo9a13ye.fsf@zuse.dina.kvl.dk> (raw)
In-Reply-To: Wes Hardaker's message of 31 Jan 1997 11:23:55 +0100
>>>>> "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?
It is very desirable to always have a proper References header, much
software can do nice things with it (like threading). I doubt there
is any practical use of also having an In-Reply-To header, as the
software that can use it most likely also handles References.
next prev parent reply other threads:[~1997-01-31 11:25 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 [this message]
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=rjlo9a13ye.fsf@zuse.dina.kvl.dk \
--to=abraham@dina.kvl.dk \
--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).