From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Oliver Hartkopp <oliver@hartkopp.net>
Cc: Romano Giannetti <romanol@upcomillas.es>,
"H. Peter Anvin" <hpa@zytor.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
akpm@linux-foundation.org, Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] Kernel naming convention in the merge phase
Date: Mon, 12 May 2008 22:56:12 +0200 [thread overview]
Message-ID: <4828AEEC.2010705@s5r6.in-berlin.de> (raw)
In-Reply-To: <48282C69.2070006@hartkopp.net>
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/
next prev parent reply other threads:[~2008-05-12 20:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 22:20 [RFC] Kernel naming convention in the merge phase Oliver Hartkopp
2008-04-30 23:47 ` 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 [this message]
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=4828AEEC.2010705@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver@hartkopp.net \
--cc=romanol@upcomillas.es \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.