Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754568AbXFUXco (ORCPT ); Thu, 21 Jun 2007 19:32:44 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751000AbXFUXch (ORCPT ); Thu, 21 Jun 2007 19:32:37 -0400 Received: from dsl081-033-126.lax1.dsl.speakeasy.net ([64.81.33.126]:46248 "EHLO bifrost.lang.hm" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750929AbXFUXcg (ORCPT ); Thu, 21 Jun 2007 19:32:36 -0400 Date: Thu, 21 Jun 2007 16:32:50 -0700 (PDT) From: david@lang.hm X-X-Sender: dlang@asgard.lang.hm To: Jan Engelhardt cc: Jesper Juhl , =?ISO-8859-1?Q?Zolt=E1n_HUBERT?= , linux-kernel@vger.kernel.org Subject: Re: Please release a stable kernel Linux 3.0 In-Reply-To: Message-ID: References: <200706212349.54983.zoltan.hubert@zzaero.com> <9a8748490706211529yca0588dgd1f7e0b86f7e4a62@mail.gmail.com> MIME-Version: 1.0 Content-Type: MULTIPART/Mixed; BOUNDARY="-699020219-721175904-1182468615=:26568" Content-ID: Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1757 Lines: 42 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. ---699020219-721175904-1182468615=:26568 Content-Type: TEXT/PLAIN; CHARSET=UTF-8; format=flowed Content-Transfer-Encoding: 8BIT Content-ID: On Fri, 22 Jun 2007, Jan Engelhardt wrote: > On Jun 22 2007 00:29, Jesper Juhl wrote: >> On 21/06/07, Zoltán HUBERT wrote: >> [snip] >>> All people who might read this know that traditionally >>> stable releases are even numbered and development branches >>> are odd numbered. This changed during late develoment of >>> 2.6, according to my analysis because of the "invention" of >>> GIT which was itself necessary because of BitKeeper (insert >>> ooooooooold flame-wars here) and which allowed very dynamic >>> develoment. >> [...] >> I myself have argued that we should be focusing more on stability and >> regression fixing, but I'm not so sure that a 2.6.7 devel branch would >> solve this. In general the 2.6.x.y -stable kernels seem to be doing >> the job pretty good. > > For my part, I think the 2.6. did not go as well as the 2.6., > beginning with x=16. you misunderstood the even/odd it was never 2.x.y with y odd/even being stable / development, it was the x being even/odd to indicate stable / development. all 2.6.x are stable, all 2.5.x were development. David Lang ---699020219-721175904-1182468615=:26568-- - 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/