From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: Doc bug: gnus-registry-ignored-groups, gnus-registry-unfollowed-groups, nnmail-split-fancy-with-parent-ignore-groups
Date: Wed, 10 Jan 2007 10:57:11 -0500 [thread overview]
Message-ID: <g69r6u2lvs8.fsf@dhcp-65-162.kendall.corp.akamai.com> (raw)
In-Reply-To: <v91wm3rakr.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Wed\, 10 Jan 2007 01\:26\:28 +0100")
On 9 Jan 2007, reinersteib+from-uce@imap.cc wrote:
> Could you please apply the doc fixes in v5-10 as well, if
> appropriate?
Since gnus-registry.el is not in the manual, and these are just doc
fixes, I don't think it's necessary. If you disagree, I'll do it,
it's not a problem.
There's a little more work I need to do on the registry before I make
it official (with manual entries, etc.). This includes the
g-r-ignored-groups parameter I mentioned, more support for easy
search/add/delete of entry attributes, and cleaning up the code.
Unfortunately I don't have an ETA on that.
Ted
next prev parent reply other threads:[~2007-01-10 15:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <86zm8smand.fsf@ketchup.de.uu.net>
[not found] ` <g69d55nkhi5.fsf@dhcp-65-162.kendall.corp.akamai.com>
2007-01-10 0:26 ` Reiner Steib
2007-01-10 15:57 ` Ted Zlatanov [this message]
2007-01-10 21:48 ` Reiner Steib
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=g69r6u2lvs8.fsf@dhcp-65-162.kendall.corp.akamai.com \
--to=tzz@lifelogs.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).