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: <4828A4CF.9010103@zytor.com>
Date:	Mon, 12 May 2008 13:13:03 -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:
> 
> This is no real detail. How can -rc0 break a naming scheme for a robot,
> when -rc1 doesn't?
> 

Because of things like:

- regexp patterns like -(rc|pre)([1-9][0-9]*)
- using zero to mean "no rc/pre"
- assuming 1 is the immediate decendent of the previous one

So on, etc, yadda yadda...

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