From: Ted Zlatanov <tzz@lifelogs.com>
Cc: Jake Colman <colman@ppllc.com>, ding@gnus.org
Subject: Re: registry questions
Date: Mon, 03 Nov 2003 21:40:37 -0500 [thread overview]
Message-ID: <4nhe1ksvoa.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <87n0bd5acy.fsf@mulligatwani.msrl.com> (Michael Shields's message of "Mon, 03 Nov 2003 22:57:17 +0000")
On Mon, 03 Nov 2003, shields@msrl.com wrote:
> In message <4nfzh546vs.fsf@lockgroove.bwh.harvard.edu>,
> Ted Zlatanov <tzz@lifelogs.com> wrote:
>> The drafts group probably makes no sense for the registry. There
>> will be a "queue" group eventually that will queue articles that
>> need to be split in a different backend.
>
> Note that there is already a "queue" group, which is used to hold
> messages that cannot be sent yet because you're unplugged.
Maybe I can use that code, because it's a very similar purpose -
delayed processing of articles. For unplugged messages, they are to
be sent; for messages that are to be split to a different backend
they need to be moved.
Maybe a new header (or reuse of an existing one) could be used,
X-Gnus-Move-To: or something like that?
Ted
prev parent reply other threads:[~2003-11-04 2:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-03 13:57 Jake Colman
2003-11-03 18:57 ` Ted Zlatanov
2003-11-03 20:31 ` Kai Grossjohann
2003-11-03 22:57 ` Michael Shields
2003-11-04 2:40 ` Ted Zlatanov [this message]
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=4nhe1ksvoa.fsf@lockgroove.bwh.harvard.edu \
--to=tzz@lifelogs.com \
--cc=colman@ppllc.com \
--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).