Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261386AbVAMSNw (ORCPT ); Thu, 13 Jan 2005 13:13:52 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261432AbVAMSNm (ORCPT ); Thu, 13 Jan 2005 13:13:42 -0500 Received: from mailhost.ntl.com ([212.250.162.8]:2010 "EHLO mta09-winn.mailhost.ntl.com") by vger.kernel.org with ESMTP id S261386AbVAMSK2 (ORCPT ); Thu, 13 Jan 2005 13:10:28 -0500 Message-ID: <41E6D5F8.2040901@gentoo.org> Date: Thu, 13 Jan 2005 20:11:36 +0000 From: Daniel Drake User-Agent: Mozilla Thunderbird 1.0 (X11/20041209) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andres Salomon Cc: linux-kernel@vger.kernel.org Subject: Re: 2.6.10-as1 References: <1105605448.7316.13.camel@localhost> In-Reply-To: <1105605448.7316.13.camel@localhost> X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1011 Lines: 25 Hi, Andres Salomon wrote: > I'm announcing a new kernel tree; -as. The goal of this tree is to form > a stable base for vendors/distributors to use for their kernels. In > order to do this, I intend to include only security fixes and obvious > bugfixes, from various sources. I do not intend to include driver > updates, large subsystem fixes, cleanups, and so on. Basically, this is > what I'd want 2.6.10.1 to contain. After all of the recent discussion it's nice to see someone step up and do this :) Thanks a lot, I'm sure I will find it useful when producing gentoo's kernel packages.. Just one suggestion- maybe could you distinguish security patches from bugfixes? I.e. prepend or append the security patches with "sec" or something? Thanks, Daniel - 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/