linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Romano Giannetti <romanol@upcomillas.es>
To: "H. Peter Anvin" <hpa@zytor.com>
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, 07 May 2008 14:39:24 +0200	[thread overview]
Message-ID: <1210163964.14371.1.camel@localhost> (raw)
In-Reply-To: <481A06C0.6070500@zytor.com>


On Thu, 2008-05-01 at 11:06 -0700, H. Peter Anvin wrote:

> Most of the robots don't have access to git.
> 
> > For me a 2.6.25-gitX looks like a snapshot that leads to a 2.6.25.1 and 
> > _not_ to a 2.6.26-rc1.
> 
> Tough.  It's a naming convention quite old (we had -bk before -git, too.)

What about a -rc0 as the first commit after a release? Will help a lot
automatic installing scripts...

Romano 
 
-- 
Sorry for the disclaimer --- ¡I cannot stop it!



--
La presente comunicación tiene carácter confidencial y es para el exclusivo uso del destinatario indicado en la misma. Si Ud. no es el destinatario indicado, le informamos que cualquier forma de distribución, reproducción o uso de esta comunicación y/o de la información contenida en la misma están estrictamente prohibidos por la ley. Si Ud. ha recibido esta comunicación por error, por favor, notifíquelo inmediatamente al remitente contestando a este mensaje y proceda a continuación a destruirlo. Gracias por su colaboración.

This communication contains confidential information. It is for the exclusive use of the intended addressee. If you are not the intended addressee, please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited by law. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy this message. Thank you for your cooperation. 

  reply	other threads:[~2008-05-07 12:40 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 [this message]
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=1210163964.14371.1.camel@localhost \
    --to=romanol@upcomillas.es \
    --cc=akpm@linux-foundation.org \
    --cc=greg@kroah.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oliver@hartkopp.net \
    --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).