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

Date:	Mon, 12 May 2008 13:39:21 +0200
From:	Oliver Hartkopp <oliver@...tkopp.net>
To:	Romano Giannetti <romanol@...omillas.es>
CC:	"H. Peter Anvin" <hpa@...or.com>,
	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

Romano Giannetti wrote:
> On Thu, 2008-05-01 at 11:06 -0700, H. Peter Anvin wrote:
>
>   
>> Most of the robots don't have access to git.
>>
>>     
>>> For me a 2.6.25-gitX looks like a snapshot that leads to a 2.6.25.1 and 
>>> _not_ to a 2.6.26-rc1.
>>>       
>> Tough.  It's a naming convention quite old (we had -bk before -git, too.)
>>     
>
> What about a -rc0 as the first commit after a release? Will help a lot
> automatic installing scripts...
>
>   

Yes - this was also my intention. I don't have any preferences if the 
first commit after a release is named -merge or -rc0. But it should 
point out that we're leaving the former stable release.

Regards,
Oliver

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