Gnus development mailing list
 help / color / mirror / Atom feed
From: Per Abrahamsen <abraham@dina.kvl.dk>
Cc: ding@ifi.uio.no
Subject: Re: Sparse threads
Date: Wed, 10 Jan 1996 19:41:52 +0100	[thread overview]
Message-ID: <199601101841.TAA11446@ssv4.dina.kvl.dk> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of 08 Jan 1996 13:08:19 +0100


>>>>> "LMI" == Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:

LMI> I thought filling in "gaps" in threads (without reading further
LMI> headers) would be a) a major project and b) slow as hell, but it
LMI> turned out to be quite simple to do.  Just some References munging,
LMI> some sorting (since Message-IDs late in the References headers are
LMI> probably more reliable (with regards to what sequence articles have
LMI> been posted) than early Message-IDs), and some threading.  

This is great, it has been one of my major wishes since Gnus 3.13!  I
have even attempted to implement it several times, but each time
concluded that it was too hard.  

I hope it works with the various values of `gnus-fetch-old-headers',
in particular (setq gnus-fetch-old-headers 'some) should give you all
the same articles as trn finds.


  reply	other threads:[~1996-01-10 18:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-01-08 12:08 Lars Magne Ingebrigtsen
1996-01-10 18:41 ` Per Abrahamsen [this message]
1996-01-11 21:25   ` Lars Magne Ingebrigtsen
1996-01-19 13:15     ` Greg Stark
1996-01-20  5:25       ` Lars Magne Ingebrigtsen
1996-01-20 14:09         ` Greg Stark
1996-01-20 22:07           ` d. hall
1996-01-22  2:51             ` Lars Magne Ingebrigtsen
1996-01-22  2:51           ` Lars Magne Ingebrigtsen

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=199601101841.TAA11446@ssv4.dina.kvl.dk \
    --to=abraham@dina.kvl.dk \
    --cc=ding@ifi.uio.no \
    /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).