From: Lee Revell <rlrevell@joe-job.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Christoph Hellwig <hch@infradead.org>,
Erik Mouw <erik@harddisk-recovery.com>,
Adrian Bunk <bunk@stusta.de>, Domen Puncer <domen@coderock.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [patch] maintainers: remove moderated arm list
Date: Tue, 04 Jan 2005 20:19:13 -0500 [thread overview]
Message-ID: <1104887953.18410.13.camel@krustophenia.net> (raw)
In-Reply-To: <1104883649.17166.105.camel@localhost.localdomain>
On Wed, 2005-01-05 at 00:07 +0000, Alan Cox wrote:
> On Maw, 2005-01-04 at 21:13, Lee Revell wrote:
> > Agreed. Besides, there are _very_ effective solutions to the spam
> > problem. man spamassassin.
>
> You realise current generation spam generator tools actually grab and
> build spamassassin and then feed the spam through it adjusting it until
> it passes ?
>
> Please don't tell mailing list admins how to run lists.
>
Apologies for the offtopic post.
Lee
next prev parent reply other threads:[~2005-01-05 1:23 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-25 17:08 [patch] maintainers: remove moderated arm list Domen Puncer
2004-12-25 17:21 ` Russell King
2004-12-25 17:34 ` Domen Puncer
2005-01-03 17:54 ` [patch] " Adrian Bunk
2005-01-03 18:25 ` Russell King
2005-01-04 17:33 ` Adrian Bunk
2005-01-05 12:52 ` Horst von Brand
2005-01-04 8:54 ` Erik Mouw
2005-01-04 9:00 ` Christoph Hellwig
2005-01-04 9:25 ` Russell King
2005-01-04 9:33 ` Christoph Hellwig
2005-01-04 10:19 ` Russell King
2005-01-05 9:20 ` Jes Sorensen
2005-01-05 14:04 ` Alan Cox
2005-01-06 9:20 ` Russell King
2005-01-04 21:13 ` Lee Revell
2005-01-05 0:07 ` Alan Cox
2005-01-05 1:19 ` Lee Revell [this message]
2005-01-04 22:03 ` Alan Cox
2005-01-04 9:08 ` Russell King
2005-01-04 9:37 ` Miles Bader
2005-01-04 9:48 ` Dave Airlie
2005-01-04 10:18 ` Erik Mouw
2005-01-04 13:05 ` Miles Bader
2005-01-04 13:37 ` Erik Mouw
2005-01-04 22:03 ` Alan Cox
2005-01-09 20:26 ` Pavel Machek
2004-12-26 16:50 ` Alan Cox
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=1104887953.18410.13.camel@krustophenia.net \
--to=rlrevell@joe-job.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bunk@stusta.de \
--cc=domen@coderock.org \
--cc=erik@harddisk-recovery.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.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 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.