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>] [day] [month] [year] [list]

Message-Id: <200810200905.01322.denys@visp.net.lb>
Date:	Mon, 20 Oct 2008 09:05:01 +0300
From:	Denys Fedoryshchenko <denys@...p.net.lb>
To:	linux-kernel@...r.kernel.org
Subject: Re: [RFC] Kernel version numbering scheme change

Let me post my stupid idea :-) Dont hit me :-)

releasenum.branch.subreleasename(chars)+subreleasenumber(numbers).deepersubreleasename.....

1.vanilla.pre3
1.vanilla.rc1
1.vanilla.0 (stable release)
1.vanilla.fix1 (first stable patch)
2.mm.rc5
2.netdev.git2342424323423423

current versions, let's start from 2.6.27 looks like
2627.vanilla.0

next will be 2628


It is easy to parse, easy to find out what is a "base" release number, for 
patches and other trees

for mm's, for example, based on unstable kernels
mm.2.rc5.mm2
easy to understand, that it is mm branch, based on stable release 2, release 
candidate 5, mm patchset N2

Since Linus told there is no need in 2.6, probably there is no reason to keep 
even this numbers.
--
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/