linux-kernel - Re: Linux 2.6.32-rc3

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: <4ACB626C.8090503@s5r6.in-berlin.de>
Date:	Tue, 06 Oct 2009 17:29:48 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Dirk Hohndel <hohndel@...radead.org>,
	Len Brown <lenb@...nel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 2.6.32-rc3

Ingo Molnar wrote:
> I.e. i think it's a fact that right now our release version is highly 
> deceptive during the merge window.
[...]
> One option would be to make LOCALVERSION_AUTO compulsory.
> 
> Or to add a tweak to the naming, something like:
> 
>  v2.6.31
>  v2.6.31+
>  v2.6.32-rc1
>  v2.6.32-rc1+
[...]
> ... for the sole purpose of warning people that anything they pull after 
> v2.6.31 got released is (wildly!) not vanilla v2.6.31 anymore.

If this scheme is meant to be something on which people can rely on,
everybody who commits to a tree from which Linus pulls from would have
to base their branches onto those ...+ commits, always.
-- 
Stefan Richter
-=====-==--= =-=- --==-
http://arcgraph.de/sr/
--
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/