Gnus development mailing list
 help / color / mirror / Atom feed
From: Toby Speight <streapadair@gmx.net>
Subject: Re: Thread gathering and subject matching
Date: 22 Jan 2001 15:40:29 +0000	[thread overview]
Message-ID: <s8snmb389e.fsf@lanber.cam.eu.citrix.com> (raw)
In-Reply-To: Greg Stark's message of "07 Jan 2001 01:49:46 -0500"

0> In article <87ofxj26wl.fsf@stark.yi.org>,
0> Greg Stark <URL:mailto:gsstark@mit.edu> ("Greg") wrote:

Greg> How come Gnus is clever enough to put most of the posts into a
Greg> single thread, but not clever enough to avoid repeating the same
Greg> subject in my summary buffer a dozen times?

Because, in your example, the subjects were *not* the same - some
respondents have added spaces before the word "start":

Greg>    [  24: Henrique M Holschuh ] Re: Bug#81397: [authorization] fails silently for normal users, cannot start server
Greg>      <  51: Eray Ozkural (exa)  >
Greg>      <  44: Eray Ozkural (exa)  >
Greg>        [  18: Hamish Moffatt      ]
Greg>          [  39: Eray Ozkural (exa)  ] Re: Bug#81397: [authorization] fails silently for normal users, cannot  start server
Greg>            [  43: Hamish Moffatt      ] Re: Bug#81397: [authorization] fails silently for normal users, cannot start server
Greg>
Greg>
Greg>
Greg> Also, how come it managed to reparent enough of them but about a
Greg> page lower there are three more, that it missed?

These ones not only have a different subject, but also lack threading
information (In-Reply-To, References).  One thing that I think *is*
Gnus's fault is that thread gathering is done only against thread
roots - WIBNI orphans were also gathered against subthreads when the
subject changes?



      reply	other threads:[~2001-01-22 15:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-07  6:49 Greg Stark
2001-01-22 15:40 ` Toby Speight [this message]

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=s8snmb389e.fsf@lanber.cam.eu.citrix.com \
    --to=streapadair@gmx.net \
    /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).