Re: what to call it after 2.6.23 but before 2.6.24-rc1?

[Linus Torvalds]

On Sat, 20 Oct 2007, Erez Zadok wrote:
>
> Linus, is there a preferred name to refer to the kernel version in your tree
> after 2.6.23 is out (and the official 2.6.23.y git was created) but before
> you release 2.6.24-rc1?

Well, since you can only get one of those kernels in two ways, there's a 
very unambiguous naming policy.

 - if you got one of the nightly snapshots, name it by the snapshot name 
   (I still call them "nightly snapshots", but they do in fact happen 
   twice a day if there have been changes, so that's not technically 
   correct)

   So the last snapshot would be linux-2.6.23-git15

   This is an exact name, because you can go to kernel.org and look up the 
   exact commit ID that was used to generate it (there's an "ID" file 
   associated with each snapshot there).

   For bonus points, if you report a bug against such a snapshot, look up 
   the ID yourself, so that others don't have to do that..

 - if you are a git user, and got it that way, just use the git name, and 
   use "git describe" to get it.

   So my current head is called "v2.6.23-6562-g8add244" which tells you 
   three things:
     (a) it's based on 2.6.23
     (b) there's been 6562 commits since 2.6.23
     (c) the top-of-tree abbreviated commit is "8add244".

> I've seen online references to it as "2.6.24", "2.6.24++", "2.6.24-rc0", 
> etc.

Yeah, please don't use those names. They don't actually tell anything 
about where in the cycle it is, and as you can see above, there's been 
6500+ commits since 2.6.23, so saying "2.6.23-rc0" or similar really isn't 
very helpful if anybody actually cares about just where in the release 
cycle you are.

			Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/