All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Hartkopp <oliver@hartkopp.net>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Romano Giannetti <romanol@upcomillas.es>,
	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 21:48:16 +0200	[thread overview]
Message-ID: <48289F00.9010406@hartkopp.net> (raw)
In-Reply-To: <48289C59.5040401@zytor.com>

H. Peter Anvin wrote:
> Oliver Hartkopp wrote:
>> H. Peter Anvin wrote:
>>> Oliver Hartkopp wrote:
>>>>
>>>> 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.
>>>>
>>>
>>> Either way it'll take a bunch of work.
>>
>> Can you give any details?
>>
>> Why does tagging a -rc0 create any effort for anyone - except half a
>> minute for Linus?
>>
>
> Because it breaks all the robots which rely on the kernel naming scheme.
>

This is no real detail. How can -rc0 break a naming scheme for a robot,
when -rc1 doesn't?

Btw. you don't seem to have any interest in my suggestion and obviously
Linus, Greg and Andrew also do not have any interest in something like a
-rc0. So i won't create any new noise about that topic from my side.

Thanks anyway,
Oliver


  reply	other threads:[~2008-05-12 19:48 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 [this message]
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=48289F00.9010406@hartkopp.net \
    --to=oliver@hartkopp.net \
    --cc=akpm@linux-foundation.org \
    --cc=greg@kroah.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --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.