mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesper Juhl <jj@chaosbits.net>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Should SUBLEVEL be removed for 3.x ?
Date: Mon, 11 Jul 2011 01:26:55 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LNX.2.00.1107110124420.2818@swampdragon.chaosbits.net> (raw)
In-Reply-To: <20110710160906.952bb38a.rdunlap@xenotime.net>

On Sun, 10 Jul 2011, Randy Dunlap wrote:

> On Mon, 11 Jul 2011 00:07:13 +0200 (CEST) Jesper Juhl wrote:
> 
> > Hi
> > 
> > If the plan is that the new kernel is going to be 3.0 (3.x) and the 
> > -stable kernels then get to tack on a third digit with EXTRAVERSION, then 
> > it seems to me that the main Makefile should get rid of SUBLEVEL - or?
> > 
> > Or is the plan to ditch EXTRAVERSION for -stable kernels and have them use 
> > SUBLEVEL instead?
> > 
> > There are a few scripts that need fixing if SUBLEVEL goes the way of the 
> > Dodo, but I didn't want to start fixing those without a clear indication 
> > of whether or not SUBLEVEL is going to/should die.
> > 
> > So what's going to happen to SUBLEVEL/EXTRAVERSION?
> 
> I cannot answer this, but I'd certainly like to see a clear answer
> since I also have several scripts that need such attention.
> 
And besides our own personal scriots there's also stuff like
	scripts/patch-kernel and Documentation/kbuild/makefiles.txt
that need updating.

-- 
Jesper Juhl <jj@chaosbits.net>       http://www.chaosbits.net/
Don't top-post http://www.catb.org/jargon/html/T/top-post.html
Plain text mails only, please.


  reply	other threads:[~2011-07-10 23:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-10 22:07 Jesper Juhl
2011-07-10 23:09 ` Randy Dunlap
2011-07-10 23:26   ` Jesper Juhl [this message]
2011-07-13 21:53 ` Jesper Juhl
2011-07-15 17:33   ` Linus Torvalds
2011-07-17 16:10     ` Jesper Juhl

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=alpine.LNX.2.00.1107110124420.2818@swampdragon.chaosbits.net \
    --to=jj@chaosbits.net \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.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

all inboxes | Powered by JetHome®