Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: gnus-registry-split-fancy-with-parent  and sender/subject
Date: Mon, 18 Oct 2010 21:03:14 +0200	[thread overview]
Message-ID: <m38w1vxr0t.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <87fww5q5gc.fsf@andy.bu.edu>

Andrew Cohen <cohen@andy.bu.edu> writes:

> I rely heavily on splitting mail according to the registry (the
> principal reason I do client side splitting) and just recently started
> tracking sender and subject. I notice that splitting according to
> references/in-reply-to obeys the ignore-groups variable, while splitting
> by sender and subject do not. Is there a reason for this? If not I would
> propose making them all behave the same way.

I don't use the registry stuff, so I can't say whether this is
intentional or not.  But the patch looks reasonable, so I'll apply it.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen




  reply	other threads:[~2010-10-18 19:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-16 19:54 Andrew Cohen
2010-10-18 19:03 ` Lars Magne Ingebrigtsen [this message]
2010-10-19 14:17   ` 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=m38w1vxr0t.fsf@quimbies.gnus.org \
    --to=larsi@gnus.org \
    --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).