public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "René Rebe" <rene@exactcode.de>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>,
	Roman Zippel <zippel@linux-m68k.org>,
	akpm@osdl.org
Subject: Re: kbuild / KERNELRELEASE not rebuild correctly anymore
Date: Sun, 15 Jan 2006 15:26:34 +0100	[thread overview]
Message-ID: <200601151526.34236.rene@exactcode.de> (raw)
In-Reply-To: <20060115123133.GB15881@mars.ravnborg.org>

Hi,

On Sunday 15 January 2006 13:31, Sam Ravnborg wrote:
> > I'm curious, aside rsbac, what in the .config is altering the
> > KERNELRELEASE?
>
> CONFIG_LOCALVERSION
> CONFIG_LOCALVERSION_AUTO

Ah, ok - I feared something less obviously more complex. Do we need this 
options at all? People can still just edit the EXTRAVERSION line in the 
Makefile - at least I always did so ...

Also you have not answered if you expect to patch away the version output in 
the *config frontends ...

Yours,

-- 
René Rebe - Rubensstr. 64 - 12157 Berlin (Europe / Germany)
            http://www.exactcode.de | http://www.t2-project.org
            +49 (0)30  255 897 45

  reply	other threads:[~2006-01-15 14:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-15  9:51 kbuild / KERNELRELEASE not rebuild correctly anymore René Rebe
2006-01-15 10:05 ` Sam Ravnborg
2006-01-15 10:41   ` René Rebe
2006-01-15 11:19     ` Sam Ravnborg
2006-01-15 12:12       ` René Rebe
2006-01-15 12:31         ` Sam Ravnborg
2006-01-15 14:26           ` René Rebe [this message]
2006-01-15 23:29             ` Kyle Moffett
2006-01-16 11:15             ` [PATCH] kbuild: create .kernelrelease at *config step Sam Ravnborg
2006-01-15 10:13 ` kbuild / KERNELRELEASE not rebuild correctly anymore Grant Coady
2006-01-15 10:42   ` René Rebe

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=200601151526.34236.rene@exactcode.de \
    --to=rene@exactcode.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=torvalds@osdl.org \
    --cc=zippel@linux-m68k.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