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]

Message-ID: <48289C59.5040401@zytor.com>
Date:	Mon, 12 May 2008 12:36:57 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Oliver Hartkopp <oliver@...tkopp.net>
CC:	Romano Giannetti <romanol@...omillas.es>,
	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

Oliver Hartkopp wrote:
> H. Peter Anvin wrote:
>> Oliver Hartkopp wrote:
>>>
>>> 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.
>>>
>>
>> Either way it'll take a bunch of work.
> 
> Can you give any details?
> 
> Why does tagging a -rc0 create any effort for anyone - except half a 
> minute for Linus?
> 

Because it breaks all the robots which rely on the kernel naming scheme.

Again.

You already asked.

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