mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Sam Ravnborg" <sam@ravnborg.org>
To: "Geert Uytterhoeven" <geert@linux-m68k.org>
Cc: "Sam Ravnborg" <sam@ravnborg.org>,
	"Linux Kernel Development" <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:14:44 +0200 (CEST)	[thread overview]
Message-ID: <49210.194.237.142.7.1094044484.squirrel@194.237.142.7> (raw)
In-Reply-To: <Pine.GSO.4.58.0409011341140.15681@waterleaf.sonytel.be>

> On Tue, 31 Aug 2004, Sam Ravnborg wrote:
>> 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
>
> Wouldn't it make more sense the other way around (i.e. first append
> $(srctree)/localversion-*, then append $(objtree)/localversion*)?
>
> Hmm, from a second thought the order depends on what your most interested
> in:
> building kernels with different configs, or building kernels from
> different
> sources.
>
My rationale was that the config used would vary more than the source.
I also thought about sorting the files - but if Andrew for example
start using this it would maybe come in the middle.
Therefore this more simple approach.

   Sam



  reply	other threads:[~2004-09-01 13:14 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 [this message]
2004-09-01 13:43 ` Jan-Benedict Glaw
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=49210.194.237.142.7.1094044484.squirrel@194.237.142.7 \
    --to=sam@ravnborg.org \
    --cc=akpm@osdl.org \
    --cc=geert@linux-m68k.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®