Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: Major splitting problem ... Advice please
Date: Thu, 11 Oct 2001 09:40:13 +0200	[thread overview]
Message-ID: <vafitdmvd42.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m1wv22d9x7.fsf@reader.newsguy.com> (Harry Putnam's message of "Wed, 10 Oct 2001 22:26:28 -0700")

Harry Putnam <reader@newsguy.com> writes:

> I currently use command line tools or homemade scripting to extract
> info from this pile, but it would be nice to be easily able to access
> it with gnus at times too.  By `access' here, I don't mean nndir or
> the like.  But handy smallish groups that handle well inside
> gnus. Where all manner of highlight or other special treatment/sorting
> wouldn't be a major time drag. Maybe a series of nnml groups for each
> main newsgroup or something.

Maybe the best thing to do is to write a script which extracts
threads.  Then you just keep adding threads to a group until it gets
larger than N messages, then start the next group.

Let T be an empty thread.  You find a message R (the root of the
thread) which does not have a References header.  You add it to the
thread.  So T now contains one message.  Let M be the set of
Message-ID headers for all messages in T.  You find a new message X
and you see that its References header mentions one of the Message-IDs
in M.  So you add X to T, and you add X's Message-ID to M, and repeat.

See?

kai
-- 
Linux provides a nice `poweroff' command, but where is `poweron'?



  reply	other threads:[~2001-10-11  7:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-11  5:26 Harry Putnam
2001-10-11  7:40 ` Kai Großjohann [this message]
2001-10-12  4:01   ` Harry Putnam
2001-10-11 12:02 ` Karl Kleinpaste
2001-10-11 15:54   ` Paul Jarc
2001-10-11 16:25     ` Paul Jarc
2001-10-11 16:37       ` Kai Großjohann
2001-10-12 16:44 ` Rob Browning
2001-10-13  4:28   ` Harry Putnam

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=vafitdmvd42.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    --cc=ding@gnus.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).