From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Threading without References header?
Date: 24 May 1997 12:56:47 +0200 [thread overview]
Message-ID: <m267w9jfyo.fsf@proletcult.slip.ifi.uio.no> (raw)
In-Reply-To: Hrvoje Niksic's message of 24 May 1997 11:54:24 +0200
Hrvoje Niksic <hniksic@srce.hr> writes:
> > If there is no References line, then (by definition) there is no
> > parent.
>
> Why can't Gnus use `In-Reply-Tp' for threading?
It does. Whenever I say "References" I mean "References and
In-Reply-To". Except in the cases where I don't mean that. :-)
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~1997-05-24 10:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-05-21 9:22 Kai Grossjohann
1997-05-24 3:41 ` Lars Magne Ingebrigtsen
1997-05-24 9:54 ` Hrvoje Niksic
1997-05-24 10:56 ` Lars Magne Ingebrigtsen [this message]
1997-05-24 23:43 ` Kai Grossjohann
1997-05-25 12:52 ` Lars Magne Ingebrigtsen
1997-05-25 16:41 ` Kai Grossjohann
1997-05-27 9:54 ` Lars Magne Ingebrigtsen
1997-05-27 18:53 ` Paul Franklin
1997-05-28 15:37 ` Kai Grossjohann
1997-06-01 22:20 ` Matt Simmons
1997-06-02 0:05 ` anonymous
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=m267w9jfyo.fsf@proletcult.slip.ifi.uio.no \
--to=larsi@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).