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: <20081017174226.GF2221@kroah.com>
Date:	Fri, 17 Oct 2008 10:42:26 -0700
From:	Greg KH <greg@...ah.com>
To:	"H. Peter Anvin" <hpa@...nel.org>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>, 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 Fri, Oct 17, 2008 at 09:40:32AM -0700, H. Peter Anvin wrote:
> Alan Cox wrote:
>>> So I proposed an alternative, YEAR.NUMBER.  The year is easy to keep
>> Which calendaring system ?
>
> Presumably the Gregorian one, rooted in the Common Era, but that's sort of 
> irrelevant.
>
> I think it's both visually cumbersome and has the problem that it is harder 
> to predict future releases.  The first problem can be dealt with by simply 
> subtracting 2000 from the year (Altera uses this scheme for their EDA 
> tools, and I didn't realize it for quite a while because it looked so 
> natural), but the second is still a problem.

What is the "problem" of predicting future releases?  What relies on the
actual number being "correct" some random time in the future?

thanks,

greg k-h
--
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/