Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262783AbVCDDJB (ORCPT ); Thu, 3 Mar 2005 22:09:01 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262718AbVCDC7M (ORCPT ); Thu, 3 Mar 2005 21:59:12 -0500 Received: from parcelfarce.linux.theplanet.co.uk ([195.92.249.252]:63191 "EHLO parcelfarce.linux.theplanet.co.uk") by vger.kernel.org with ESMTP id S262764AbVCDC47 (ORCPT ); Thu, 3 Mar 2005 21:56:59 -0500 Message-ID: <4227CE58.6020607@pobox.com> Date: Thu, 03 Mar 2005 21:56:24 -0500 From: Jeff Garzik User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040922 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andrew Morton CC: Alan Cox , greg@kroah.com, torvalds@osdl.org, davem@davemloft.net, linux-kernel@vger.kernel.org Subject: Re: RFD: Kernel release numbering References: <42268749.4010504@pobox.com> <20050302200214.3e4f0015.davem@davemloft.net> <42268F93.6060504@pobox.com> <4226969E.5020101@pobox.com> <20050302205826.523b9144.davem@davemloft.net> <4226C235.1070609@pobox.com> <20050303080459.GA29235@kroah.com> <4226CA7E.4090905@pobox.com> <422751C1.7030607@pobox.com> <20050303181122.GB12103@kroah.com> <20050303151752.00527ae7.akpm@osdl.org> <1109894511.21781.73.camel@localhost.localdomain> <20050303182820.46bd07a5.akpm@osdl.org> In-Reply-To: <20050303182820.46bd07a5.akpm@osdl.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1260 Lines: 36 Andrew Morton wrote: > Alan Cox wrote: > >>On Iau, 2005-03-03 at 23:17, Andrew Morton wrote: >> >>>Ideally, the 2.6.x.y maintainer wouldn't need any particular kernel >>>development skills - it's just patchmonkeying the things which maintainers >>>send him. >> >>I would disagree, and I suspect anyone else who has maintained a distro >>stable kernel would likewise. It needs one or more people who know who >>to ask about stuff, are careful, have a good grounding in bug spotting, >>races, common mistakes and know roughly how all the kernel works. >>Maintainers aren't very good at it in general and they don't see >>overlaps between areas very well. >> > > > That is all inappropriate activity for a 2.6.x.y tree as it is being > proposed. > > Am I right? All we're proposing here is a tree which has small fixups for > reasonably serious problems. Almost without exception it would consist of > backports. "thru-ports": commit to linux-2.6.x.y and get Linus to pull. Jeff - 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/