Hello,
I have configured Gnus threading like this
(setq gnus-summary-make-false-root nil
gnus-summary-thread-gathering-function 'gnus-gather-threads-by-references)
to be a bit stricter on what constitutes a thread. This has been
working perfectly for zillions of messages.
However I noted recently that Gnus fails to identify the root message
for email notifications sent out by a certain "gitlab" server that I
use. I can see that when I set gnus-summary-make-false-root to `dummy'.
Then the various replies are grouped around a dummy root, but the real
root message, while present, is not recognized.
For example the message containing the following headers
Message-ID: <merge_request_...@gitlab.kwant-project.org>
References: <reply-ecefc6162592037a62ad12961b4ec...@gitlab.kwant-project.org>
Subject: kwant | refer to PropagatingModes docstring from physics.leads.modes
(!169)
is not identified correctly as the parent of the message containing the
following
Message-ID: <1b59c2bc72f138cb93a2e667884e8...@gitlab.kwant-project.org>
In-Reply-To: <merge_request_...@gitlab.kwant-project.org>
References: <merge_request_...@gitlab.kwant-project.org>
<reply-45ca557093d0d928d3afa9b5a791f...@gitlab.kwant-project.org>
Subject: Re: kwant | refer to PropagatingModes docstring from
physics.leads.modes (!169)
Isn't this strange? Everything seems to be set correctly.
Gnus' awesome configurability allows me to work around this problem by
setting gnus-summary-make-false-root to `adopt' and
gnus-summary-thread-gathering-function to
`gnus-gather-threads-by-subject' just for this group (using group
parameters). But I would like to understand what's going on, especially
whether this is a bug in Gnus or in gitlab.
A quick unrelated question: Is this the famous d...@gnus.org mailing list, or
a separate one? Is d...@gnus.org still active?
Christoph
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
