From: Josh Sled <jsled@asynchronous.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in sys-fs/ncdu: ChangeLog ncdu-1.3.ebuild
Date: Thu, 04 Oct 2007 00:33:28 -0400 [thread overview]
Message-ID: <87lkajzeg7.fsf@phoenix.asynchronous.org> (raw)
In-Reply-To: <20071004000819.GI18289@bla.fasel.org> (Wolfram Schlich's message of "Thu\, 4 Oct 2007 02\:08\:19 +0200")
[-- Attachment #1: Type: text/plain, Size: 1335 bytes --]
Wolfram Schlich <wschlich@gentoo.org> writes:
> * Donnie Berkholz <dberkholz@gentoo.org> [2007-10-03 19:12]:
>> On 12:43 Wed 03 Oct , Wolfram Schlich wrote:
>> > And *please*, don't send such mails to this
>> > list *and* to my address in addition.
>>
>> You can add a procmail rule to detect duplicates using a cache and
>> checking Message-Id, with formail. Examples of this are all over the
>> place. It's a useful rule to have for many reasons besides this.
>
> Yeah, but it's unpredictable *which* one of the two mails makes
> it first onto my system, thus the one *not* sent to the list might
Sigh.
It is the same message, addressed To/Cc: you and/or the list, no matter which
one is delivered first. So just put all list(+private) filtering before
personal filtering.
E.g.,
# filter duplicate-message delivery; see procmailex
# "The more you know."
:0 Wh: msgid.lock
| formail -D 8192 msgid.cache
:0 He
* ^(to|from|cc):.*gentoo-dev
lists/gentoo-dev/
# other public mailing lists (more general, least specific)
# other private filters (less general, most specific)
# some might call the following 'inbox'...
:0
otherwise-unfiltered/
--
...jsled
http://asynchronous.org/ - a=jsled; b=asynchronous.org; echo ${a}@${b}
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2007-10-04 4:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Iczwi-0003B0-J9@stork.gentoo.org>
2007-10-03 8:52 ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in sys-fs/ncdu: ChangeLog ncdu-1.3.ebuild Donnie Berkholz
2007-10-03 10:43 ` Wolfram Schlich
2007-10-03 12:52 ` Mike Frysinger
2007-10-03 17:07 ` Donnie Berkholz
2007-10-04 0:08 ` Wolfram Schlich
2007-10-04 4:33 ` Josh Sled [this message]
2007-10-07 14:57 ` Alec Warner
2007-10-07 18:13 ` Chris Gianelloni
2007-10-08 3:48 ` Robert Buchholz
2007-10-11 15:23 ` Wolfram Schlich
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=87lkajzeg7.fsf@phoenix.asynchronous.org \
--to=jsled@asynchronous.org \
--cc=gentoo-dev@lists.gentoo.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