From: Miles Bader <miles.bader@necel.com>
To: ding@gnus.org
Subject: Re: Ugly In-Reply-To?
Date: Thu, 10 May 2007 11:27:20 +0900 [thread overview]
Message-ID: <buo3b25xvjr.fsf@dhapc248.dev.necel.com> (raw)
In-Reply-To: <b4mabwda2ym.fsf@jpl.org>
Katsumi Yamaoka <yamaoka@jpl.org> writes:
> BTW, I'm not sure how the In-Reply-To header is actually used.
> If anything, I consider it is a useless header, so I've never
> been adding it to outgoing messages for years.
I've always assumed that some mail clients might use In-Reply-To instead
of References for constructing thread trees (though I have no actual
evidence one way or the other).
-miles
--
自らを空にして、心を開く時、道は開かれる
next prev parent reply other threads:[~2007-05-10 2:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-07 12:51 Simon Josefsson
2007-05-10 1:21 ` Katsumi Yamaoka
2007-05-10 2:27 ` Miles Bader [this message]
2007-05-10 19:55 ` Reiner Steib
2007-05-11 0:15 ` Katsumi Yamaoka
2007-05-11 0:22 ` Katsumi Yamaoka
2007-05-11 0:28 ` Katsumi Yamaoka
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=buo3b25xvjr.fsf@dhapc248.dev.necel.com \
--to=miles.bader@necel.com \
--cc=ding@gnus.org \
/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).