From: "Ted Zlatanov" <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: registry question
Date: 16 Nov 2004 16:49:08 -0500 [thread overview]
Message-ID: <4nd5ydjwh7.fsf@lifelogs.com> (raw)
In-Reply-To: <76sm7o9gwa.fsf@newjersey.ppllc.com> (Jake Colman's message of "Fri, 05 Nov 2004 15:31:49 -0500")
On Fri, 05 Nov 2004, colman@ppllc.com wrote:
>>>>>> "TZ" == Ted Zlatanov <tzz@lifelogs.com> writes:
>
> TZ> Maybe gnus-registry-ignored-groups will help?
Sorry about that, by the way. Wrong variable name.
> TZ> I haven't had the time to write a manual section on the registry, sorry.
>
> I wish you (or someone) would. The registry is a great feature!
I'm glad you like it. If you or someone else would consider writing a
"getting started with the registry" document, I'll fill in the
technical details. I'm simply too swamped to do the whole thing.
Ted
prev parent reply other threads:[~2004-11-16 21:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-04 16:13 Jake Colman
2004-11-05 16:17 ` Ted Zlatanov
2004-11-05 20:31 ` Jake Colman
2004-11-16 21:49 ` 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=4nd5ydjwh7.fsf@lifelogs.com \
--to=tzz@lifelogs.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).