From: Tim Howe <vsync@quadium.net>
To: info-gnus-english@gnu.org
Subject: Re: threading broken in g.e.gnus
Date: Wed, 03 Apr 2013 12:36:13 -0400 [thread overview]
Message-ID: <87wqsj4lmq.fsf@rash.fl.quadium.net> (raw)
In-Reply-To: <mailman.23407.1365005109.855.info-gnus-english@gnu.org>
On 03 Apr 2013, wgreenhouse@riseup.net (W. Greenhouse) wrote:
> Tim Howe <vsync@quadium.net> writes:
>
>> I'm noticing many of the threads in here are completely broken. It
>> seems the Message-IDs are getting replaced by Mailman ones so References
>> and In-Reply-To headers are left dangling.
>
> You can try customizing `gnus-summary-thread-gathering-function'.
> Gnus's default is indeed to fall back on Subject if References are
> wrong
Thanks for that, but I was actually commenting on the munging itself,
not how Gnus is handling it on display. It seems something (GMANE?) is
chewing on the articles and replacing the Message-IDs with "Mailman"
ones, meaning that references and threading are broken non-predictably
depending on the path messages take.
--
Tim Howe
http://quadium.net/~vsync/
The lack of interest, the disdain for history is what makes computing
not-quite-a-field. [...] They have no idea where [their culture came
from] and the Internet was done so well that most people think of it
as a natural resource like the Pacific Ocean, rather than something
that was man-made. When was the last time a technology with a scale
like that was so error-free? The Web, in comparison, is a joke. The
Web was done by amateurs.
-- Alan Kay
next prev parent reply other threads:[~2013-04-03 16:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.23008.1364502994.855.info-gnus-english@gnu.org>
2013-04-03 15:40 ` threading broken in g.e.gnus (was: Can't send emails to this list via gmane?) Tim Howe
2013-04-03 16:05 ` threading broken in g.e.gnus W. Greenhouse
[not found] ` <mailman.23407.1365005109.855.info-gnus-english@gnu.org>
2013-04-03 16:36 ` Tim Howe [this message]
2013-04-03 17:38 ` W. Greenhouse
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=87wqsj4lmq.fsf@rash.fl.quadium.net \
--to=vsync@quadium.net \
--cc=info-gnus-english@gnu.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).