Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756772Ab3GQR5q (ORCPT ); Wed, 17 Jul 2013 13:57:46 -0400 Received: from zeniv.linux.org.uk ([195.92.253.2]:50409 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755905Ab3GQR5o (ORCPT ); Wed, 17 Jul 2013 13:57:44 -0400 Date: Wed, 17 Jul 2013 18:57:21 +0100 From: Al Viro To: Stefano Stabellini Cc: Steven Rostedt , Sarah Sharp , CAI Qian , David Lang , ksummit-2013-discuss@lists.linuxfoundation.org, Greg Kroah-Hartman , Darren Hart , Olivier Galibert , stable , Linux Kernel Mailing List , Willy Tarreau , Linus Torvalds , Ingo Molnar Subject: Re: [Ksummit-2013-discuss] [ATTEND] How to act on LKML Message-ID: <20130717175721.GT4165@ZenIV.linux.org.uk> References: <20130716212704.GB9371@thunk.org> <20130716224357.GK4994@xanatos> <1374015299.6458.76.camel@gandalf.local.home> <20130716231217.GL4994@xanatos> <51E5D7C8.5000306@gmail.com> <1374018809.2249.29.camel@leira.trondhjem.org> <1000066089.1803398.1374046596236.JavaMail.root@redhat.com> <20130717144849.GB16513@xanatos> <1374073771.6458.143.camel@gandalf.local.home> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1689 Lines: 34 On Wed, Jul 17, 2013 at 06:00:46PM +0100, Stefano Stabellini wrote: > On Wed, 17 Jul 2013, Steven Rostedt wrote: > > The last thing I want to do is to lower the quality of the kernel just > > to get a wider range of developers. > > Can we stop bringing the quality of the code into the discussion? No. > I think it's pretty clear that one doesn't need to be verbally abusive > in order to stop bad code from getting into the kernel. At the risk of sounding pedantic... The above is true *and* irrelevant as stated, and any attempts to read it in less irrelevant way result in statements that are absolutely non-obvious and very likely false. * some amount of bad code will be getting into the kernel, in any scenario short of complete cessation of development * there certainly are ways to prevent any given bad code from getting into the kernel, once you have identified it. Even leaving aside completely ridiculous ones ("after WW3 nobody will push that into the tree", etc.), one can always watch all trees for specific code and refuse to pull if it has slipped in. * "once you have identified it" part of the above is essential and does not scale. In other words, it's not "can we stop it from happening", it's "how much will be slippling in with given setup". And _this_ is where your position becomes completely unfounded. It's not at all clear that vague alternatives being proposed will *not* result in more crap getting in. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/