Gnus development mailing list
 help / color / mirror / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
Cc: ding@gnus.org
Subject: Re: Major splitting problem ... Advice please
Date: Fri, 12 Oct 2001 11:44:30 -0500	[thread overview]
Message-ID: <878zegyfip.fsf@raven.i.defaultvalue.org> (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:

> To cut to the chase here, I'm thinking of splitting this up into
> groups that contain one month/yr of a specific group.  

Hmm, I've been working on something similar off and on.  I was only
working on per-year splitting, and I hadn't yet decided what, if
anything, I was going to try to do about breaking threads, but I was
trying to write an elisp function using gnus calls to do the job
because I wanted to preserve all my marks.

> However, there are enough differnet date styles to make that kind of
> split pretty hard to program.  Also the problem of some messages
> that came late to a thread, landing in a different group arises.
> Keeping all thead members in one group may not even be possible,
> except by hand.  I'm not sure.

Hmm.  I had just been planning to use gnus date functions.  I hadn't
considered that those might not be sufficient.

-- 
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C  64AE 78FE E5FE F0CB A0AD



  parent reply	other threads:[~2001-10-12 16:44 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
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 [this message]
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=878zegyfip.fsf@raven.i.defaultvalue.org \
    --to=rlb@defaultvalue.org \
    --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).