linux-kernel - Re: [RFC] Kernel naming convention in the merge phase

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

Date:	Wed, 21 May 2008 09:02:42 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Pavel Machek <pavel@....cz>
CC:	Oliver Hartkopp <oliver@...tkopp.net>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	akpm@...ux-foundation.org, Greg KH <greg@...ah.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC] Kernel naming convention in the merge phase

Pavel Machek wrote:
>>
>> Foo-gitX has always been a development snapshot which 
>> *follows* Foo.
> 
> Well, unfortunately its not there in the makefile, so you can't tell
> 2.6.25 from 2.6.26-rc0...
> 
> Would 'rc0' make robots happy?
> 							Pavel
> 

It'll probably make some of them work and break others.  It's pretty 
hard-coded in most of them that the flow is from 2.6.25 -> 
2.6.26-{pre,rc}*; whether or not they permit a zero probably depends on 
if they know what is available or not (ketchup wouldn't be able to, for 
example, but the kernel.org incdiff robot *might* "just work".)

	-hpa
--
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/