| 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
| ||
|
Date: Mon, 12 May 2008 21:48:16 +0200 From: Oliver Hartkopp <oliver@...tkopp.net> To: "H. Peter Anvin" <hpa@...or.com> 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 H. Peter Anvin wrote: > 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. > This is no real detail. How can -rc0 break a naming scheme for a robot, when -rc1 doesn't? Btw. you don't seem to have any interest in my suggestion and obviously Linus, Greg and Andrew also do not have any interest in something like a -rc0. So i won't create any new noise about that topic from my side. Thanks anyway, 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/
Powered by blists - more mailing lists