From: "H. Peter Anvin" <hpa@zytor.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Oliver Hartkopp <oliver@hartkopp.net>,
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: Wed, 21 May 2008 09:02:42 -0700 [thread overview]
Message-ID: <483447A2.8060205@zytor.com> (raw)
In-Reply-To: <20080521111637.GA5416@ucw.cz>
Pavel Machek wrote:
>>
>> Foo-gitX has always been a development snapshot which
>> *follows* Foo.
>
> Well, unfortunately its not there in the makefile, so you can't tell
> 2.6.25 from 2.6.26-rc0...
>
> Would 'rc0' make robots happy?
> Pavel
>
It'll probably make some of them work and break others. It's pretty
hard-coded in most of them that the flow is from 2.6.25 ->
2.6.26-{pre,rc}*; whether or not they permit a zero probably depends on
if they know what is available or not (ketchup wouldn't be able to, for
example, but the kernel.org incdiff robot *might* "just work".)
-hpa
prev parent reply other threads:[~2008-05-21 16:03 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
2008-05-21 11:16 ` Pavel Machek
2008-05-21 16:02 ` H. Peter Anvin [this message]
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=483447A2.8060205@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver@hartkopp.net \
--cc=pavel@ucw.cz \
--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.