From: Jeff Garzik <jgarzik@pobox.com>
To: Wichert Akkerman <wichert@wiggy.net>
Cc: "Bartlomiej Zolnierkiewicz" <bzolnier@elka.pw.edu.pl>,
"Matthias-Christian Ott" <matthias.christian@tiscali.de>,
"Rogério Brito" <rbrito@ime.usp.br>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: 2.6.11rc4: irq 5, nobody cared
Date: Mon, 21 Feb 2005 15:32:52 -0500 [thread overview]
Message-ID: <421A4574.1000604@pobox.com> (raw)
In-Reply-To: <20050221194227.GH6722@wiggy.net>
Wichert Akkerman wrote:
> Previously Jeff Garzik wrote:
>
>>You should add this to your procmailrc :)
>>
>># Nuke duplicate messages
>>:0 Wh: msgid.lock
>>| $FORMAIL -D 32768 msgid.cache
>
>
> That has the nasty side-effect of spreading messages for a single
> discussion amongst many different mailboxes depending on which path
> happens to be the first to deliver an email to you.
These are _duplicate_ messages. The To/CC doesn't vary in my
experience. Therefore, sorting on To/CC always guarantees my messages
go into the correct folder.
Maybe you are thinking of reply-to-munged lists, which eliminate
duplicates by eliminating custom To/CC lists.
Jeff
next prev parent reply other threads:[~2005-02-21 20:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-20 15:56 2.6.11rc4: irq 5, nobody cared Folkert van Heusden
2005-02-20 16:40 ` Rogério Brito
2005-02-20 17:19 ` Matthias-Christian Ott
2005-02-20 18:05 ` Rogério Brito
2005-02-20 20:00 ` Matthias-Christian Ott
2005-02-21 18:43 ` Bartlomiej Zolnierkiewicz
2005-02-21 18:50 ` Jeff Garzik
2005-02-21 19:42 ` Wichert Akkerman
2005-02-21 20:32 ` Jeff Garzik [this message]
2005-02-21 21:48 ` Wichert Akkerman
2005-02-23 21:41 ` Bill Davidsen
2005-02-21 19:02 ` Rogério Brito
2005-02-23 21:19 ` Bill Davidsen
2005-02-24 16:44 ` Folkert van Heusden
2005-02-24 21:37 ` Bill Davidsen
2005-02-20 16:43 ` Arjan van de Ven
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=421A4574.1000604@pobox.com \
--to=jgarzik@pobox.com \
--cc=bzolnier@elka.pw.edu.pl \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.christian@tiscali.de \
--cc=rbrito@ime.usp.br \
--cc=wichert@wiggy.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.