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]

Message-ID: <alpine.LNX.1.10.0810181836260.27947@fbirervta.pbzchgretzou.qr>
Date:	Sat, 18 Oct 2008 18:38:53 -0400 (EDT)
From:	Jan Engelhardt <jengelh@...ozas.de>
To:	Greg KH <greg@...ah.com>
cc:	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 Friday 2008-10-17 17:44, Greg KH wrote:
>
>Sure, but by then, the 2.6.521 release will be out and we could fix it
>up by finally going to 3.0 :)

There will be no 2.6.521. Simply because the LINUX_VERSION_CODE
macro only allows for the 2nd and 3rd position to be 8 bits.

(Hooray, which means we will _automatically_ get a 2.7 after at most
229 more releases, or 3.0 after at most 63973 more releases!^{*})


{*} If you find off-by-one errors, keep them.
--
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/