From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: gnus-registry rewrite
Date: Wed, 20 Apr 2011 15:41:10 -0500 [thread overview]
Message-ID: <878vv4ejvd.fsf@lifelogs.com> (raw)
In-Reply-To: <87k4erh1b3.fsf@andy.bu.edu>
On Mon, 18 Apr 2011 14:17:04 -0400 Andrew Cohen <cohen@andy.bu.edu> wrote:
AC> I think I understand the logic in
AC> gnus-registry--split-fancy-with-parent-internal but I'm not 100%
AC> sure. The following changes seem to fix my problem that unfollowed
AC> groups are still followed. Ted, does this look right?
Yes, and thank you for the fixes. Committed.
Ted
next prev parent reply other threads:[~2011-04-20 20:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-17 13:22 Andrew Cohen
2011-04-18 18:17 ` Andrew Cohen
2011-04-20 20:41 ` Ted Zlatanov [this message]
2011-04-20 20:48 ` Ted Zlatanov
-- strict thread matches above, loose matches on Subject: below --
2011-04-05 16:28 Ted Zlatanov
2011-04-05 17:56 ` Ted Zlatanov
2011-04-06 8:10 ` Kan-Ru Chen
2011-04-06 10:53 ` Ted Zlatanov
2011-04-06 17:29 ` Kan-Ru Chen
2011-04-06 17:37 ` 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=878vv4ejvd.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).