From: Kai.Grossjohann@CS.Uni-Dortmund.DE
Subject: Re: Proposal/Request for feature for splitting to FQ groups
Date: 05 Jul 1999 11:46:32 +0200 [thread overview]
Message-ID: <vaf7lofa0p3.fsf@petty.cs.uni-dortmund.de> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "05 Jul 1999 06:49:31 +0200"
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Calling *-request-accept-article on all the messages would be
> unacceptably slow. Reeeally slow.
Hm. Sounds like your suggestion of splitting to a group first then
resplitting that group to another backend sounds like a good choice,
then.
Or is it feasible to just "leave" a message during splitting? Then
you could split in several steps: first you do all the nnml splitting,
then the nnimap splitting (on the messages which were "left" during
nnml splitting).
kai
--
Life is hard and then you die.
next prev parent reply other threads:[~1999-07-05 9:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-01 19:29 Soren Dayton
1999-07-01 20:33 ` William M. Perry
1999-07-02 23:43 ` Soren Dayton
1999-07-02 19:54 ` William M. Perry
1999-07-04 4:36 ` Lars Magne Ingebrigtsen
1999-07-04 20:01 ` Kai.Grossjohann
1999-07-05 4:49 ` Lars Magne Ingebrigtsen
1999-07-05 9:46 ` Kai.Grossjohann [this message]
1999-07-06 4:16 ` 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=vaf7lofa0p3.fsf@petty.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
/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).