public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Friesen <cfriesen@nortel.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: "Justin M. Forbes" <jmforbes@linuxtx.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.Stable and EXTRAVERSION
Date: Fri, 11 Mar 2005 14:42:58 -0600	[thread overview]
Message-ID: <423202D2.8000207@nortel.com> (raw)
In-Reply-To: <4231F7C8.7070806@tmr.com>

Bill Davidsen wrote:
> Justin M. Forbes wrote:
> 
>> With the new stable series kernels, the .x versioning is being added to
>> EXTRAVERSION.  This has traditionally been a space for local 
>> modification.
>> I know several distributions are using EXTRAVERSION for build numbers,
>> platform and assorted other information to differentiate their kernel
>> releases.
>> I would propose that the new stable series kernels move the .x version
>> information somewhere more official.  I certainly do not mind throwing
>> together a patch to support DOTVERSION or what ever people want to 
>> call it.
>> Is anyone opposed to such a change?
> 
> 
> I think it will confuse scripts which expect something local in the 4th 
> field. I confess that I have such, and that field is turned into a 
> directory name during builds, so test results are saved in a proper 
> place. I think vendors and people who care will just keep three digits, 
> and those who want the last can make their EXTRAVERSION
>    2.Joes_Bar_&_Grill_486
> or whatever is needed.

There's also the LOCALVERSION that can be set in the config file.  I've 
switched to using that, since it means one less kernel patch to port.

Chris

  reply	other threads:[~2005-03-11 20:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-09 18:53 2.6.Stable and EXTRAVERSION Justin M. Forbes
2005-03-09 19:41 ` Chris Friesen
2005-03-10  0:01 ` Chris Wright
2005-03-10  8:25 ` Andreas Gruenbacher
2005-03-14 22:16   ` Sam Ravnborg
2005-03-11 19:55 ` Bill Davidsen
2005-03-11 20:42   ` Chris Friesen [this message]
2005-03-11 20:42     ` Bill Davidsen
2005-03-15 19:51       ` Matan Peled

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=423202D2.8000207@nortel.com \
    --to=cfriesen@nortel.com \
    --cc=davidsen@tmr.com \
    --cc=jmforbes@linuxtx.org \
    --cc=linux-kernel@vger.kernel.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