Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262399AbVCCSop (ORCPT ); Thu, 3 Mar 2005 13:44:45 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262520AbVCCSnr (ORCPT ); Thu, 3 Mar 2005 13:43:47 -0500 Received: from sj-iport-2-in.cisco.com ([171.71.176.71]:27499 "EHLO sj-iport-2.cisco.com") by vger.kernel.org with ESMTP id S261408AbVCCSmF (ORCPT ); Thu, 3 Mar 2005 13:42:05 -0500 Message-Id: <200503031842.AWY46304@mira-sjc5-e.cisco.com> Reply-To: From: "Hua Zhong" To: "'Linus Torvalds'" , "'Jeff Garzik'" Cc: "'Greg KH'" , "'David S. Miller'" , , Subject: RE: RFD: Kernel release numbering Date: Thu, 3 Mar 2005 10:42:00 -0800 Organization: Cisco Systems MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4939.300 Thread-Index: AcUgDe83JHlKi2QrQ4i2pw46NoINRAAEeapw Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1543 Lines: 36 > In fact, if somebody maintained that kind of tree, especially > in BK, it would be trivial for me to just pull from it every once in a > while (like ever _day_ if necessary). But for that to work, then that > tree would have to be about so _obviously_ not wild patches that > it's a no-brainer. Alan Cox once said he would like to do it: > On Mer, 2004-10-27 at 19:37, Hua Zhong wrote: > When I said "nobody", I really meant "top kernel developers". I have not > seen anyone step up and say "I'll volunteer to maintain a 2.6 stable > release" hence the comment. I'll do it if Linus wants Do you consider having a real stable release maintainer again? If you want someone to do the job, give him a title. It's a thankless and boring job, and you can't make it worse by just hiding him somewhere. How a "stable release maintainer" works for the current model is up to you. One thought is that he picks up 2.6.x release as a start point and takes patches to make it stable, then releases it _himself_, not by Linus. Because the real work is done by him and you need to give him the authority (just like other Linux 2.x maintainers who release official kernels). But of course you still pull from his tree to make sure the bug fixes are also committed to mainline. Hua - 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/