From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Vladislav Bolkhovitin <vst@vlnb.net>
Cc: "Nicholas A. Bellinger" <nab@linux-iscsi.org>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: Spamming linux-kernel and linux-scsi by out-of-tree patches (LIO)
Date: Mon, 26 Jan 2009 09:37:14 -0600 [thread overview]
Message-ID: <1232984234.3248.18.camel@localhost.localdomain> (raw)
In-Reply-To: <497DB7D0.8000302@vlnb.net>
On Mon, 2009-01-26 at 16:17 +0300, Vladislav Bolkhovitin wrote:
> Nicholas,
>
> Could you stop spamming linux-kernel and linux-scsi mailing lists by
> patches for your out-of-tree LIO project, please?
>
> Those mailing lists are intended for patches for in-kernel components
> only, not for all out-of-tree projects, finding their ways into the
> mainline. I don't see any reason why your project should be an
> exception. Think, what a mess the kernel mailing lists would get, if all
> out-of-tree projects started sending their patches to them?
Actually, out of tree projects trying to make their way upstream are
welcome to use the various linux- mailing lists to solicit feedback and
review. This method was, for instance, how FCoE made it in.
> My personal practical concerns about your patches that they trigger my
> e-mail filters, so I have to spend on them much more time than I would want.
I've found that spamassassin does a good job of marking patches as non
spam. Also, if you're using zmailer, vger seems to have some type of
patch recognition system built in which might be worth co-opting.
James
next prev parent reply other threads:[~2009-01-26 15:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 13:17 Spamming linux-kernel and linux-scsi by out-of-tree patches (LIO) Vladislav Bolkhovitin
2009-01-26 15:37 ` James Bottomley [this message]
2009-01-26 16:08 ` Vladislav Bolkhovitin
2009-01-26 16:19 ` Arjan van de Ven
2009-01-26 16:44 ` Vladislav Bolkhovitin
2009-01-26 17:15 ` Nicholas A. Bellinger
2009-01-26 16:37 ` James Bottomley
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=1232984234.3248.18.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=vst@vlnb.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