From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
Ian Wienand <ianw@gelato.unsw.edu.au>,
Christoph Hellwig <hch@lst.de>
Subject: Re: kbuild: Support LOCALVERSION
Date: Wed, 1 Sep 2004 15:43:41 +0200 [thread overview]
Message-ID: <20040901134341.GT6985@lug-owl.de> (raw)
In-Reply-To: <20040831192642.GA15855@mars.ravnborg.org>
[-- Attachment #1: Type: text/plain, Size: 1699 bytes --]
On Tue, 2004-08-31 21:26:43 +0200, Sam Ravnborg <sam@ravnborg.org>
wrote in message <20040831192642.GA15855@mars.ravnborg.org>:
> The following patch combines the request from several people.
> If you place a file named localversion* in the root of your
> soruce tree or the root of your output tree the text included in this
> file will be appended to KERNELRELEASE.
>
> LOCALVERSION was originally introduced by Ian Wienand <ianw@gelato.unsw.edu.au>
>
> This allows one to put a short string in localversion identifying this
> particular configuration "-smpacpi", or to identify applied patches
> to the source "-llat-np".
>
> More specifically:
> $(srctree)/localversion-lowlatency contains "-llat"
> $(srctree)/localversion-scheduler-nick constins "-np"
>
> $(objtree)/localversion contains "-smpacpi"
>
> Resulting KERNELRELEASE would be:
> 2.6.8.rc1-smpacpi-llat-np
Basically: I love it. Maybe it would also be good (in the longer term)
to introduce a config name into one of the Kconfig files, which is
preserved in the .config file (eg. SuSE does something like that and
even while I'm not a SuSE user, it's really dandy at some times, esp.
for things like "SMP-4GB", "VAX-KA4x" and the like). It's basically like
adding the defconfig_* name to some of the variables :-)
MfG, JBG
PS: When will the package support show up?
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481 _ O _
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg _ _ O
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak! O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-09-01 13:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-31 19:26 Sam Ravnborg
2004-09-01 1:08 ` Ian Wienand
2004-09-01 1:24 ` Ian Wienand
2004-09-01 5:11 ` Sam Ravnborg
2004-09-01 11:44 ` Geert Uytterhoeven
2004-09-01 13:14 ` Sam Ravnborg
2004-09-01 13:43 ` Jan-Benedict Glaw [this message]
2004-09-01 14:56 ` Sam Ravnborg
2004-09-02 10:42 ` [PATCH] " Ian Wienand
2004-09-05 19:43 ` Sam Ravnborg
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=20040901134341.GT6985@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=akpm@osdl.org \
--cc=hch@lst.de \
--cc=ianw@gelato.unsw.edu.au \
--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
all inboxes | Powered by JetHome®