linux-kernel - Re: [RFC] Kernel version numbering scheme change

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 21 Oct 2008 22:16:49 +0300
From:	Felipe Balbi <felipe.balbi@...ia.com>
To:	ext Stefan Richter <stefanr@...6.in-berlin.de>
Cc:	felipe.balbi@...ia.com, Greg KH <greg@...ah.com>,
	Willy Tarreau <w@....eu>, Alan Cox <alan@...rguk.ukuu.org.uk>,
	Steven Noonan <steven@...inklabs.net>,
	Adrian Bunk <bunk@...nel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC] Kernel version numbering scheme change

On Tue, Oct 21, 2008 at 09:11:52PM +0200, ext Stefan Richter wrote:
> Felipe Balbi wrote:
>> On Mon, Oct 20, 2008 at 02:06:48PM -0700, Greg KH wrote:
>>> On Mon, Oct 20, 2008 at 11:54:00PM +0300, Felipe Balbi wrote:
>>>> when we move to 2.7, we know it'll be the start
>>>> for the 2.8 kernel series.
>>> Um, did you not get the memo 3 years ago saying we are changing our
>>> development model and there will not be a 2.7 development series?
>>>
>>> Damm, I thought I had printed it out and placed it on everyone's chairs.
>>> Those pesky cleaners must have picked it up and recycled it, sorry about
>>> that...
>>>
>>>> Just like the migration from 2.4 to 2.5.
>>> Please don't bring up the dark ages again, many of us went through
>>> things back then that have taken a lot of counseling to be able to get
>>> over.
>>
>> sorry if i'm developing linux kernel for as long as you are. It's really
>> not my business how many hours of counseling you had to attend to get
>> over a version numbering change.
>
> The switch from 2.2/2.3/2.4/2.5 to 2.6.x was not a change of numbering 
> scheme, it was a change of the development model.  2.4 and 2.5 were two 
> parallel mainlines.  2.6.x is a single mainline, and there won't be two 
> mainlines again in any foreseeable future.

at least now you gave me the reasons and I got the point. Thanks for
clarifying.

-- 
balbi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/