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 22:56:12 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Oliver Hartkopp <oliver@...tkopp.net>
CC:	Romano Giannetti <romanol@...omillas.es>,
	"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

Oliver Hartkopp wrote:
> Romano Giannetti wrote:
>> What about a -rc0 as the first commit after a release? Will help a lot
>> automatic installing scripts...

What is "a lot"?  Maybe the solution is to switch from sh to bash.

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

2.6.25-git8 says exactly this.  It is a nightly generated patch on top 
of 2.6.25, retrieved from the then current linux-2.6.git.

If you see a -gitX then you know that this is not a release, it is only 
a snapshot.

Your proposed -rc0 on the other hand has, in addition to the drawbacks 
which H. Peter already mentioned, the problem that there would be 
suddenly two release names for one and the same release.  This would 
only increase confusion.

Anyway.  You can always add your own tags in your cloned repository.
-- 
Stefan Richter
-=====-==--- -=-= -==--
http://arcgraph.de/sr/
--
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/