From: Russell King <rmk@arm.linux.org.uk>
To: Mike Castle <dalgoda@ix.netcom.com>, linux-kernel@vger.kernel.org
Subject: Re: [patch] 2.4 add suffix for uname -r
Date: Sun, 6 May 2001 18:08:03 +0100 [thread overview]
Message-ID: <20010506180803.A1179@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.33.0105060334390.1549-100000@asdf.capslock.lan> <3437.989135106@ocs3.ocs-net> <20010506101217.H3988@marowsky-bree.de> <20010506013605.C31385@thune.mrc-home.com>
In-Reply-To: <20010506013605.C31385@thune.mrc-home.com>; from dalgoda@ix.netcom.com on Sun, May 06, 2001 at 01:36:05AM -0700
On Sun, May 06, 2001 at 01:36:05AM -0700, Mike Castle wrote:
> On Sun, May 06, 2001 at 10:12:17AM +0200, Lars Marowsky-Bree wrote:
> > You assign a new EXTRAVERSION to the new kernel you are building, and keep the
> > old kernel at the old name.
>
> Except that some patches (ie, RAID, -ac) use EXTRAVERSION. There needs to
> be a new variable, say USERVERSION, that will *ONLY* be set during make
> USERVERSION=foo.
Ok, so we have $(VERSION).$(MINOR).$(PATCHLEVEL)$(EXTRAVERSION)$(USERVERSION).
Isn't this the same as $(VERSION).$(MINOR).$(PATCHLEVEL)$(EXTRAVERSION) where
$(EXTRAVERSION) has $(USERVERSION) appended?
In other words:
EXTRAVERSION=-ac4-build1
You can extend EXTRAVERSION infinitely, but after the first 10 or so
characters, it starts to get silly.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2001-05-06 17:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-06 7:15 [patch] 2.4 add suffix for uname -r Keith Owens
2001-05-06 7:35 ` Mike A. Harris
2001-05-06 7:45 ` Keith Owens
2001-05-06 8:12 ` Lars Marowsky-Bree
2001-05-06 8:36 ` Mike Castle
2001-05-06 9:01 ` Lars Marowsky-Bree
2001-05-06 17:08 ` Russell King [this message]
2001-05-06 9:16 ` Mike A. Harris
2001-05-07 17:29 ` Pavel Roskin
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=20010506180803.A1179@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=dalgoda@ix.netcom.com \
--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