From: Karl Kleinpaste <karl@justresearch.com>
Subject: Re: threading based on `in-reply-to' headers
Date: 22 Oct 1999 10:01:53 -0400 [thread overview]
Message-ID: <vxkpuy7cx4e.fsf@beaver.jprc.com> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "21 Oct 1999 18:39:47 +0200"
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 355 bytes --]
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> I don't know whether it helps to add the in-reply-to header to
> gnus-extra-headers.
No. On the other hand, it doesn't seem to me that it would be too
hard to add an (or ...) clause around accessing the overview-supplied
references with an in-reply-to extraction from the current article.
next prev parent reply other threads:[~1999-10-22 14:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-21 10:11 NAGY Andras
1999-10-21 16:39 ` Kai Großjohann
1999-10-22 14:01 ` Karl Kleinpaste [this message]
1999-10-25 14:41 ` NAGY Andras
1999-10-25 20:51 ` Kai Großjohann
1999-11-06 22:20 ` 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=vxkpuy7cx4e.fsf@beaver.jprc.com \
--to=karl@justresearch.com \
/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).