public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Michal Marek <mmarek@suse.cz>
Cc: Kamal Mostafa <kamal@canonical.com>,
	linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
	Luis Henriques <luis.henriques@canonical.com>
Subject: Re: [PATCH] Makefile: version.h macros KERNEL_EXTRAVERSION, LINUX_EXTRAVERSION_CODE
Date: Fri, 20 Jun 2014 13:56:19 -0700	[thread overview]
Message-ID: <20140620205619.GB17904@kroah.com> (raw)
In-Reply-To: <53A49ABB.8070704@suse.cz>

On Fri, Jun 20, 2014 at 10:34:03PM +0200, Michal Marek wrote:
> Dne 20.6.2014 17:47, Kamal Mostafa napsal(a):
> > On Fri, 2014-06-20 at 11:39 +0200, Michal Marek wrote:
> >> Why don't you guys simply increment the third digit in the extended
> >> stable tree and get support for KERNEL_VERSION() for free? You always
> >> start after the respective stable branch has reached EOL, don't you?
> > 
> > Yes, we only start after the stable branch has reached EOL.
> > 
> > We don't increment the third integer for the extended-stable branches
> > (we add a fourth integer instead) in order to avoid the possibility of a
> > collision if Greg KH were to ever release a "special" post-EOL version
> > of one of his branches.
> 
> The maintainers of 2.6.32.y, 3.2.y and 3.12.y have taken that risk and
> it has been working fine so far ;-).

Those maintainers are doing so on the kernel.org infrastructure, with my
help and encouragement, unlike these Canonical "stable" trees, so their
risk was a lot less :)

thanks,

greg k-h

      reply	other threads:[~2014-06-20 20:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-19 14:44 [PATCH] Makefile: version.h macros KERNEL_EXTRAVERSION, LINUX_EXTRAVERSION_CODE Kamal Mostafa
2014-06-20  9:39 ` Michal Marek
2014-06-20 15:47   ` Kamal Mostafa
2014-06-20 20:34     ` Michal Marek
2014-06-20 20:56       ` Greg KH [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=20140620205619.GB17904@kroah.com \
    --to=greg@kroah.com \
    --cc=kamal@canonical.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luis.henriques@canonical.com \
    --cc=mmarek@suse.cz \
    /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