From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: mail splitting to another backend
Date: Thu, 17 Apr 2003 15:09:52 -0400 [thread overview]
Message-ID: <4nhe8xdjpb.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <m3lly9rm03.fsf@multivac.cwru.edu> (Paul Jarc's message of "Thu, 17 Apr 2003 14:56:06 -0400")
On Thu, 17 Apr 2003, prj@po.cwru.edu wrote:
> I think mail splitting really ought to be redone. It should be
> controlled by Gnus proper rather than an individual select method.
> (There's too much policy in backends generally.) Splitting to
> multiple select methods would go naturally with that.
OK, so multiple splitting is not in the near future? I'm OK with
that, I just want to know so I can write the registry
split-with-parent function.
There's only two places where splitting is done, AFAIK: nnmail and
nnimap splitting (regular and fancy).
Ted
next prev parent reply other threads:[~2003-04-17 19:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-17 16:59 Ted Zlatanov
2003-04-17 18:56 ` Paul Jarc
2003-04-17 19:09 ` Ted Zlatanov [this message]
2003-04-17 19:53 ` Paul Jarc
2003-04-17 19:41 ` Simon Josefsson
2003-04-17 20:22 ` Ted Zlatanov
2003-04-17 20:31 ` Paul Jarc
2003-04-18 8:56 ` Simon Josefsson
2003-04-18 10:06 ` Kai Großjohann
2003-04-18 21:33 ` server parameter vs. server variable (was: mail splitting to another backend) Reiner Steib
2003-04-18 23:03 ` server parameter vs. server variable Paul Jarc
2003-04-20 14:35 ` Kai Großjohann
2003-04-20 15:11 ` Jesper Harder
2003-04-21 20:23 ` texinfo markup fixes (was: server parameter vs. server variable) Reiner Steib
2003-04-21 22:05 ` texinfo markup fixes Jesper Harder
2003-04-22 0:31 ` François Pinard
2003-04-22 0:36 ` Jesper Harder
2003-04-22 0:53 ` François Pinard
2003-04-18 17:12 ` mail splitting to another backend Ted Zlatanov
2003-04-18 22:48 ` Paul Jarc
2003-04-18 23:00 ` Ted Zlatanov
2003-04-27 3:09 ` Lars Magne Ingebrigtsen
2003-04-29 18:42 ` Ted Zlatanov
2003-05-01 6:55 ` 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=4nhe8xdjpb.fsf@lockgroove.bwh.harvard.edu \
--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).