From: Michael Shields <shields@msrl.com>
Cc: ding@gnus.org
Subject: Re: registry questions
Date: Mon, 03 Nov 2003 22:57:17 +0000 [thread overview]
Message-ID: <87n0bd5acy.fsf@mulligatwani.msrl.com> (raw)
In-Reply-To: <4nfzh546vs.fsf@lockgroove.bwh.harvard.edu> (Ted Zlatanov's message of "Mon, 03 Nov 2003 13:57:43 -0500")
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.
--
Shields.
next prev parent reply other threads:[~2003-11-03 22:57 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 [this message]
2003-11-04 2:40 ` Ted Zlatanov
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=87n0bd5acy.fsf@mulligatwani.msrl.com \
--to=shields@msrl.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).