From: Tom Koelman <tkoelman@xs4all.nl>
Subject: Re: Can thread gathering use In-Reply-To: <message-id>?
Date: Mon, 20 May 2002 16:24:46 +0200 [thread overview]
Message-ID: <uit5ioq1d.fsf@assurancetourix.xs4all.nl> (raw)
In-Reply-To: <m3661kx6fo.fsf@defun.localdomain>
Jesper Harder wrote:
> tkoelman@xs4all.nl (Tom Koelman) writes:
>
>> Jesper Harder wrote:
>>
>>> tkoelman@xs4all.nl (Tom Koelman) writes:
>>>
>>>> On inspection of the reply I noticed that it didn't have its
>>>> References header set, but did have a header called In-Reply_To:
>>>> with the correct message-id.
>>>>
>>>> Is there some way to make gnus use this information?
>>>
>>> Hmm, I would have thought Gnus already does it.
>>
>> You are right, thanks.
>> I had set gnus-summary-thread-gathering-function to
>> gnus-gather-threads-by-references. When I turned that off the thread
>> was gathered nicely.
>
> Hmm, I think this patch should make work with
> gnus-gather-threads-by-references, too:
[patch snipped]
Jesper, I applied your patch to gnus-sum.el. I use Oort 0.06 btw. In
.gnus I set gnus-summary-thread-gathering-function to
gnus-gather-threads-by-reference.
Now when I enter gnus.ding on quimby and look at articles
<Pine.LNX.4.44.0205151452570.4915-100000@yxa.extundo.com> and
<uk7q53f3s.fsf@axis.com>, they show up in my summary buffer like this:
! [ 31: Niklas Morberg ] Gathering very loose threads
! [ 40: Simon Josefsson ] Re: Gathering very loose threads
while the second one has In-Reply-To: <uk7q53f3s.fsf@axis.com>. Does
this mean I didn't apply you patch correctly or is my understanding of
thread gathering incorrect?
Regards,
Tom
next prev parent reply other threads:[~2002-05-20 14:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-15 17:05 Tom Koelman
2002-05-15 18:53 ` Jesper Harder
2002-05-15 20:14 ` Tom Koelman
2002-05-15 21:25 ` Andras BALI
2002-05-16 7:01 ` Tom Koelman
2002-05-19 1:38 ` Jesper Harder
2002-05-20 14:24 ` Tom Koelman [this message]
2002-05-26 18:07 ` Jesper Harder
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=uit5ioq1d.fsf@assurancetourix.xs4all.nl \
--to=tkoelman@xs4all.nl \
/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).