From: Jake Colman <colman@ppllc.com>
Subject: registry questions
Date: Mon, 03 Nov 2003 08:57:38 -0500 [thread overview]
Message-ID: <76ad7dy2p9.fsf@newjersey.ppllc.com> (raw)
I've been using the gnus-registry and I have a few questions. Please point
me to any docs that I might have missed.
1) Can/should the registry be purged? Or is it self-maintaining?
2) I see that some groups can be specified as NOT feeding the registry.
Under what circumstances would I want to do this and why?
3) Let's say I have a messages that is initially filed (by split-fancy) to
a generic work folders and I move it to a project-specific folder. Is the
registry supposed to ensure that follow-ups to that original message
automatically get filed to the project-specific folder? That's my
understanding yet it does not seem to be doing that. I'm assuming that it
is because my registry is not yet "trained". What will cause it be
trained? Simply reading messages over a period of time?
Thanks!
...Jake
--
Jake Colman
Principia Partners LLC Phone: (201) 209-2467
Harborside Financial Center Fax: (201) 946-0320
902 Plaza Two E-mail: colman@ppllc.com
Jersey City, NJ 07311 www.principiapartners.com
next reply other threads:[~2003-11-03 13:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-03 13:57 Jake Colman [this message]
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
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=76ad7dy2p9.fsf@newjersey.ppllc.com \
--to=colman@ppllc.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).