From: Bill Davidsen <davidsen@tmr.com>
To: Wichert Akkerman <wichert@wiggy.net>
Cc: "Jeff Garzik" <jgarzik@pobox.com>,
"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: Wed, 23 Feb 2005 16:41:12 -0500 [thread overview]
Message-ID: <421CF878.1080109@tmr.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.
It depends on how you process your mail, if you move to folders with
determanent logic, checking various lists in order, then it always does
the same thing. If you use the list header it could do what you suggest.
I personally push a lot of the mailing lists to a news (usenet) server,
since it allows a single copy of a message to be indexed in multiple
groups, and some clients will skip what you have seen better than others.
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
prev parent reply other threads:[~2005-02-23 21:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050220155600.GD5049@vanheusden.com>
[not found] ` <20050220164010.GA17806@ime.usp.br>
[not found] ` <4218C692.9040106@tiscali.de>
2005-02-20 18:05 ` 2.6.11rc4: irq 5, nobody cared 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
2005-02-21 21:48 ` Wichert Akkerman
2005-02-23 21:41 ` Bill Davidsen [this message]
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=421CF878.1080109@tmr.com \
--to=davidsen@tmr.com \
--cc=bzolnier@elka.pw.edu.pl \
--cc=jgarzik@pobox.com \
--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 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).