From: "Ted Zlatanov" <tzz@lifelogs.com>
Subject: Re: Split based on threads?
Date: 21 Jun 2004 10:39:27 -0400 [thread overview]
Message-ID: <4ny8mhug9s.fsf@lifelogs.com> (raw)
In-Reply-To: <m33c4spjme.fsf@defun.localdomain> (Jesper Harder's message of "Sat, 19 Jun 2004 00:49:13 +0200")
On Sat, 19 Jun 2004, harder@ifa.au.dk wrote:
> Chris Green <cmg@dok.org> writes:
>
>> Ted Zlatanov has written gnus-registry.el which contains a
>> gnus-registry-split-fancy-with-parent which will look in the
>> references and in-reply-to fileds for that.
>
> There's also `nnmail-split-fancy-with-parent'
> <info://gnus/Fancy+Mail+Splitting> -- I don't how it differs from the
> registry version.
nnmail-s-f-w-p doesn't track article copy/move/delete operations, and
only works for nnmail.
Ted
next prev parent reply other threads:[~2004-06-21 14:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-18 20:12 Norman Walsh
2004-06-18 21:17 ` Chris Green
2004-06-18 22:49 ` Jesper Harder
2004-06-21 14:39 ` Ted Zlatanov [this message]
2004-06-21 15:52 ` Reiner Steib
2004-06-21 17:35 ` Ted Zlatanov
2004-06-24 14:17 ` Kai Grossjohann
2004-06-24 14:43 ` Reiner Steib
2004-06-24 16:06 ` Ted Zlatanov
2004-06-25 6:23 ` Kai Grossjohann
2004-06-21 14:43 ` Ted Zlatanov
2004-06-18 21:20 ` Jonas Steverud
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=4ny8mhug9s.fsf@lifelogs.com \
--to=tzz@lifelogs.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).