linux-kernel - what to call it after 2.6.23 but before 2.6.24-rc1?

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-next>] [day] [month] [year] [list]

Message-Id: <200710202154.l9KLsZoF005751@agora.fsl.cs.sunysb.edu>
Date:	Sat, 20 Oct 2007 17:54:35 -0400
From:	Erez Zadok <ezk@...sunysb.edu>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org
Subject: what to call it after 2.6.23 but before 2.6.24-rc1?

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?  I've seen online references to it as "2.6.24",
"2.6.24++", "2.6.24-rc0", etc.  Since your top-level Makefile still says
"2.6.23", it is sometimes a bit confusing when one is testing code against
your tree as well as the previously released stable kernel.  I usually will
stick a localversion file in my cloned copy of your tree, saying
"2.6.24-pre-rc" or so.  Perhaps you can come up with a definitive name for
this "limbo" state and put it in your Makefile?

Anyway, 'tis just a minor quibble (which I hope won't start yet another
major "naming" flame war :-0

Thanks,
Erez.
-
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/