Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262279AbUJZO3V (ORCPT ); Tue, 26 Oct 2004 10:29:21 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262280AbUJZO3V (ORCPT ); Tue, 26 Oct 2004 10:29:21 -0400 Received: from holomorphy.com ([207.189.100.168]:39396 "EHLO holomorphy.com") by vger.kernel.org with ESMTP id S262279AbUJZO3U (ORCPT ); Tue, 26 Oct 2004 10:29:20 -0400 Date: Tue, 26 Oct 2004 07:28:41 -0700 From: William Lee Irwin III To: Ed Tomlinson Cc: Chuck Ebbert <76306.1226@compuserve.com>, Bill Davidsen , linux-kernel Subject: Re: My thoughts on the "new development model" Message-ID: <20041026142841.GH17038@holomorphy.com> References: <200410260142_MC3-1-8D2A-45C2@compuserve.com> <200410260644.47307.edt@aei.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200410260644.47307.edt@aei.ca> Organization: The Domain of Holomorphy User-Agent: Mutt/1.5.6+20040722i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 995 Lines: 22 On Tuesday 26 October 2004 01:40, Chuck Ebbert wrote: >> Sure, the next release will (may?) fix these bugs, but it will >> definitely add a whole set of new ones. On Tue, Oct 26, 2004 at 06:44:46AM -0400, Ed Tomlinson wrote: > To my mind this just points out the need for a bug fix branch. e.g. a > branch containing just bug/security fixes against the current stable > kernel. It might also be worth keeping the branch active for the n-1 > stable kernel too. > PS. we could call this the Bug/Security or bs kernels. This has been very explicitly encouraged numerous times and no one has taken up the task. Someone actually doing something about this for once may be helpful to quell the worries of people such as we're hearing from. -- wli - 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/