From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752478AbZAZPhd (ORCPT ); Mon, 26 Jan 2009 10:37:33 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751625AbZAZPhS (ORCPT ); Mon, 26 Jan 2009 10:37:18 -0500 Received: from accolon.hansenpartnership.com ([76.243.235.52]:42616 "EHLO accolon.hansenpartnership.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751546AbZAZPhR (ORCPT ); Mon, 26 Jan 2009 10:37:17 -0500 Subject: Re: Spamming linux-kernel and linux-scsi by out-of-tree patches (LIO) From: James Bottomley To: Vladislav Bolkhovitin Cc: "Nicholas A. Bellinger" , linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org In-Reply-To: <497DB7D0.8000302@vlnb.net> References: <497DB7D0.8000302@vlnb.net> Content-Type: text/plain Date: Mon, 26 Jan 2009 09:37:14 -0600 Message-Id: <1232984234.3248.18.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 (2.22.3.1-1.fc9) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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