From: Ami Fischman <usenet@fischman.org>
Subject: Re: A T more intelligent than ^ ?
Date: Sat, 08 Feb 2003 18:04:42 -0800 [thread overview]
Message-ID: <m3fzqycipx.fsf@fischman.org> (raw)
In-Reply-To: <m3wukatsez.fsf@quimbies.gnus.org>
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
[...]
> Not quite -- `A T' uses the normal Gnus threading code, which
> examines References (and if you're not using NOV) In-Reply-To. `^'
> also does this, but References and/or In-Reply-To may be broken in
> interesting ways, so it is possible that `A T' gives different
> results than `^'. Sometimes better, sometimes worse, I'd have
> thought.
The message I'm using (the followup with missing References header) has no
In-Reply-To header either, so A T must also be looking at the subject header
to determine threading. But, given that sometimes `^' just gives up,
couldn't we have it at least attempt to pick up the nearest article that A T
finds? Seems like a logical fallback to me...
To emphasize, neither In-Reply-To nor References appears in the headers of
the followup at all. The complete list of headers (after gnus pulled it in)
are: X-From-Line, Return-Path, Delivered-To, Received, X-Gnus-Mail-Source,
Message-Id, X-Mailer, Date, From, To, Subject, Mime-Version, Content-Type,
Content-Transfer-Encoding, Content-Disposition, Lines, and Xref. Nothing
about what this message is a reply or followup to...
Cheers,
--
Ami Fischman
usenet@fischman.org
next prev parent reply other threads:[~2003-02-09 2:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-08 0:39 Ami Fischman
2003-02-08 20:43 ` Lars Magne Ingebrigtsen
2003-02-09 2:04 ` Ami Fischman [this message]
2003-02-11 1:22 ` Lars Magne Ingebrigtsen
2003-02-11 9:22 ` Ami Fischman
2003-02-22 20:36 ` Lars Magne Ingebrigtsen
2003-02-22 22:45 ` Ami Fischman
2003-02-22 22:49 ` Lars Magne Ingebrigtsen
2003-02-11 16:57 ` David Abrahams
2003-02-22 20:37 ` 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=m3fzqycipx.fsf@fischman.org \
--to=usenet@fischman.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).