From: Oliver Hartkopp <oliver@hartkopp.net>
To: Linus Torvalds <torvalds@linux-foundation.org>,
akpm@linux-foundation.org, Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: [RFC] Kernel naming convention in the merge phase
Date: Thu, 01 May 2008 00:20:03 +0200 [thread overview]
Message-ID: <4818F093.3070105@hartkopp.net> (raw)
Hi all,
i wonder about the Kernel naming convention in the merge phase before
the -rc1 is officially tagged by Linus.
Won't it be more precisely to name the current snapshot
2.6.26-merge-git16 instead of 2.6.25-git16?
It is not that i would suggest to have a new git tag in this merge phase
but only the Makefile should be changed at the beginning of this phase
to identify the ongoing work for the 2.6.26:
------
diff --git a/Makefile b/Makefile
index d3634cd..b8c85a4 100644
--- a/Makefile
+++ b/Makefile
@@ -1,8 +1,8 @@
VERSION = 2
PATCHLEVEL = 6
-SUBLEVEL = 25
-EXTRAVERSION =
-NAME = Funky Weasel is Jiggy wit it
+SUBLEVEL = 26
+EXTRAVERSION = -merge
+NAME = unnamed
# *DOCUMENTATION*
# To see a list of typical targets execute "make help"
------
Introducing the new '-merge' version _that_ early helps to avoid the
version confusion in /lib/modules and also allows people to work with
kernel version depended stuff in a very early phase.
Regards,
Oliver
next reply other threads:[~2008-04-30 22:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 22:20 Oliver Hartkopp [this message]
2008-04-30 23:47 ` [RFC] Kernel naming convention in the merge phase H. Peter Anvin
2008-05-01 9:08 ` Oliver Hartkopp
2008-05-01 18:06 ` H. Peter Anvin
2008-05-07 12:39 ` Romano Giannetti
2008-05-12 11:39 ` Oliver Hartkopp
2008-05-12 15:33 ` H. Peter Anvin
2008-05-12 18:37 ` Oliver Hartkopp
2008-05-12 19:36 ` H. Peter Anvin
2008-05-12 19:48 ` Oliver Hartkopp
2008-05-12 20:13 ` H. Peter Anvin
2008-05-12 20:56 ` Stefan Richter
2008-05-21 11:16 ` Pavel Machek
2008-05-21 16:02 ` H. Peter Anvin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4818F093.3070105@hartkopp.net \
--to=oliver@hartkopp.net \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).