Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: "J.B. Moreno" <planb@newsreaders.com>
Subject: Re: Broken threading [was: Unbelievable.]
Date: Mon, 22 Jul 2002 14:22:54 -0400	[thread overview]
Message-ID: <220720021422540572%planb@newsreaders.com> (raw)
In-Reply-To: <m37kjo7i2i.fsf@jeeves.decathlon>

In article <m37kjo7i2i.fsf@jeeves.decathlon>, 
 Tom Hardy <rhardy@mailandnews.com> wrote:

> "J.B. Moreno" <planb@newsreaders.com> writes:
> 
> >  Thomas Yan <tyan@twcny.rr.com> wrote:
> > 
-snip what to do with References-
> > > Something like: Keep the first (oldest) reference and the last
> > > (newest) 3 references.
> > 
> > That is the minimum GNKSA requirement
-snip-
> > Both the GNKSA and USEFOR recommend that trimming be done by removing
> > the 2nd to oldest ID until you've reached whatever limit you are using.
> 
> Here it differed.  Gnus removed the 6th reference, not the 2nd.

Compliant with a previous draft from USEFOR -- it was thought by some
that it would help with threading (it doesn't).

> I had thought to remove more in the hope of avoiding the truncation
> problem with older newsreaders.  Bad idea?

Not necessarily -- if you comply with the minimum GNKSA requirement,
then threading will work in the vast majority of cases, as will a good
percentage of the other things done to/with the References header.

Of course, the more you leave in the more cases that it will work with,
and in *this* particular case I don't think older software was the
problem -- I think that Dorothy tried to trim it by hand and messed up.

Also note that there is no sure fire way of avoiding the truncation --
a previous version of Mac OE had a problem with long id's (for instance
those from pine) and corrupted the immediate precursor.

My recommendation is to stick to not causing any problems yourself and
removing any known problems, and leave it at that (letting Gnus handle
the rest).

-- 
J.B. Moreno


  parent reply	other threads:[~2002-07-22 18:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <GzEKu1.4w1@kithrup.com>
     [not found] ` <m0ele2p78z.fsf_-_@localhost.twcny.rr.com>
     [not found]   ` <m3ele0bjiw.fsf@jeeves.decathlon>
     [not found]     ` <86it3cbeob.fsf@sergyar.ckdhr.com>
     [not found]       ` <m08z47l0ft.fsf@localhost.twcny.rr.com>
     [not found]         ` <m3n0sn6i53.fsf@jeeves.decathlon>
2002-07-20 21:53           ` Thomas Yan
     [not found]             ` <210720021441512431%planb@newsreaders.com>
     [not found]               ` <m37kjo7i2i.fsf@jeeves.decathlon>
2002-07-22 18:22                 ` J.B. Moreno [this message]
     [not found]             ` <m3u1mtlr3j.fsf@defun.localdomain>
     [not found]               ` <m0y9c2gu7k.fsf@localhost.twcny.rr.com>
     [not found]                 ` <m3fzy99j2f.fsf@defun.localdomain>
     [not found]                   ` <240720022348365027%planb@newsreaders.com>
2002-08-01  1:28                     ` Tom Hardy
2002-08-19  4:22                       ` J.B. Moreno

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=220720021422540572%planb@newsreaders.com \
    --to=planb@newsreaders.com \
    /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).