Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261273AbVCBXsb (ORCPT ); Wed, 2 Mar 2005 18:48:31 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261300AbVCBXov (ORCPT ); Wed, 2 Mar 2005 18:44:51 -0500 Received: from fire.osdl.org ([65.172.181.4]:22489 "EHLO smtp.osdl.org") by vger.kernel.org with ESMTP id S261260AbVCBXnp (ORCPT ); Wed, 2 Mar 2005 18:43:45 -0500 Date: Wed, 2 Mar 2005 15:44:58 -0800 (PST) From: Linus Torvalds To: Lars Marowsky-Bree cc: Kernel Mailing List Subject: Re: RFD: Kernel release numbering In-Reply-To: <20050302225846.GK17584@marowsky-bree.de> Message-ID: References: <20050302225846.GK17584@marowsky-bree.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 870 Lines: 24 On Wed, 2 Mar 2005, Lars Marowsky-Bree wrote: > > If the users wouldn't even have to know, why do it? Who will benefit > from this, then? They don't _have_ to know. But both users and developers can take advantage of this to time their patches. > I think a better approach, and one which is already working out well in > practice, is to put "more intrusive" features into -mm first, and only > migrate them into 2.6.x when they have 'stabilized'. That wouldn't change. But we still have the issue of "they have to be released sometime". This makes it clear to everybody when to merge, and when to calm down. Linus - 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/