Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262512AbVCCKjx (ORCPT ); Thu, 3 Mar 2005 05:39:53 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262520AbVCCKjw (ORCPT ); Thu, 3 Mar 2005 05:39:52 -0500 Received: from smartmx-04.inode.at ([213.229.60.36]:32207 "EHLO smartmx-04.inode.at") by vger.kernel.org with ESMTP id S262512AbVCCKiv (ORCPT ); Thu, 3 Mar 2005 05:38:51 -0500 Subject: Re: RFD: Kernel release numbering From: Bernhard Schauer Reply-To: schauer@acousta.at To: lkml In-Reply-To: References: Content-Type: text/plain Date: Thu, 03 Mar 2005 11:38:58 +0100 Message-Id: <1109846338.6053.11.camel@FC3-bernhard-1.acousta.local> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 (2.0.2-3) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 588 Lines: 15 As far as I understand the numbering scheme, the 2.5 kernel leads to 2.6 series. Why not just reactivate the 2.5 kernel (Starting with i.e. 2.5.112 which will lead to 2.6.12)? There will be no change visible to end-users and developers - IMO - are more flexible in any case. (I know I totally ignore some basic thoughts with that "idea".) - 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/