From: Willy Tarreau <w@1wt.eu>
To: Zach Brown <zach.brown@oracle.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: bogofilter ate 3/5
Date: Wed, 6 Sep 2006 07:00:44 +0200 [thread overview]
Message-ID: <20060906050044.GC604@1wt.eu> (raw)
In-Reply-To: <44FE5019.6010404@oracle.com>
On Tue, Sep 05, 2006 at 09:35:37PM -0700, Zach Brown wrote:
>
> There was a 3/5 but the bogofilter decided it was spam. It made it into
> the linux-aio archive:
>
> http://marc.theaimsgroup.com/?l=linux-aio&m=115750084710650&w=2
>
> What should I have done to avoid the spam regexes and what should I do
> now that I have a patch that makes them angry?
I don't know. IMHO, bogofilter should only add a header so that people
who want to filter can and those who don't want to will get all the
messages. Spam has never been a real problem for me on LKML, but loss
of messages and patches will certainly be. I would rather have the choice
to not filter anything :-/
Willy
next prev parent reply other threads:[~2006-09-06 5:00 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-05 23:57 [RFC 0/5] dio: clean up completion phase of direct_io_worker() Zach Brown
2006-09-05 23:57 ` [RFC 1/5] dio: centralize completion in dio_complete() Zach Brown
2006-09-05 23:57 ` [RFC 2/5] dio: call blk_run_address_space() once per op Zach Brown
2006-09-05 23:57 ` [RFC 3/5] dio: formalize bio counters as a dio reference count Zach Brown
2006-09-05 23:57 ` Zach Brown
2006-09-05 23:57 ` [RFC 4/5] dio: remove duplicate bio wait code Zach Brown
2006-09-05 23:57 ` Zach Brown
2006-09-05 23:57 ` [RFC 5/5] dio: only call aio_complete() after returning -EIOCBQUEUED Zach Brown
2006-09-06 4:35 ` bogofilter ate 3/5 Zach Brown
2006-09-06 5:00 ` Willy Tarreau [this message]
2006-09-06 7:22 ` Mike Galbraith
2006-09-08 22:16 ` Matthias Andree
2006-09-06 7:36 ` [RFC 0/5] dio: clean up completion phase of direct_io_worker() Suparna Bhattacharya
2006-09-06 16:36 ` Zach Brown
2006-09-06 14:57 ` Jeff Moyer
2006-09-06 16:46 ` Zach Brown
2006-09-06 18:13 ` Jeff Moyer
-- strict thread matches above, loose matches on Subject: below --
2006-09-06 5:37 bogofilter ate 3/5 Rick Ellis
2006-09-06 18:00 ` Willy Tarreau
2006-09-06 18:04 ` Willy Tarreau
2006-09-06 18:56 ` ellis
2006-09-06 19:15 ` Chase Venters
2006-09-06 20:56 ` Krzysztof Halasa
2006-09-06 22:05 ` Chase Venters
2006-09-07 11:55 ` Krzysztof Halasa
2006-09-07 13:46 ` Chase Venters
2006-09-07 22:33 ` Krzysztof Halasa
2006-09-07 22:37 ` Chase Venters
2006-09-07 22:58 ` Krzysztof Halasa
2006-09-07 23:02 ` Matti Aarnio
2006-09-07 13:58 ` Stuart MacDonald
2006-09-07 14:27 ` Chase Venters
2006-09-07 17:35 ` Stuart MacDonald
2006-09-07 18:25 ` Chase Venters
2006-09-07 21:05 ` Stuart MacDonald
2006-09-07 9:52 ` Matti Aarnio
2006-09-06 20:13 ` Willy Tarreau
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=20060906050044.GC604@1wt.eu \
--to=w@1wt.eu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zach.brown@oracle.com \
/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.