From: Reiner Steib <reinersteib+gmane@imap.cc>
To: ding@gnus.org
Subject: Re: patch proposed: gnus-summary-limit-to-from-to
Date: Tue, 29 May 2007 07:52:34 +0200 [thread overview]
Message-ID: <v9y7j8gorh.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <b4mabvoqobv.fsf@jpl.org>
On Tue, May 29 2007, Katsumi Yamaoka wrote:
> Isn't it better to be `gnus-summary-limit-to-from-to-cc'? In
> addition, isn't there a use of excluding ones matching a regexp?
[...]
> I tried improving it modifying `gnus-summary-limit-to-recipient'.
[...]
> How about adding it to No Gnus?
If you didn't take code from Loic's suggestion, please add it.
Otherwise we might need papers from Loic.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2007-05-29 5:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-28 16:34 Loic Dachary
2007-05-29 3:51 ` Katsumi Yamaoka
2007-05-29 5:52 ` Reiner Steib [this message]
2007-05-29 9:17 ` Loic Dachary
2007-05-29 9:57 ` Katsumi Yamaoka
2007-05-29 11:32 ` Loic Dachary
2007-05-29 12:06 ` Katsumi Yamaoka
2007-05-29 12:16 ` Loic Dachary
2007-05-29 12:27 ` Katsumi Yamaoka
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=v9y7j8gorh.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--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).