[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4B951143.1050807@suse.cz>
Date: Mon, 08 Mar 2010 16:01:23 +0100
From: Michal Marek <mmarek@...e.cz>
To: paulmck@...ux.vnet.ibm.com
Cc: linux-kernel@...r.kernel.org, zippel@...ux-m68k.org, mingo@...e.hu,
akpm@...ux-foundation.org, torvalds@...ux-foundation.org,
geert@...ux-m68k.org, elendil@...net.nl, cloos@...loos.com
Subject: Re: [PATCH 0/2] v4 kconfig: place git SHA1 in .config output if in
SCM
On 5.3.2010 20:43, Paul E. McKenney wrote:
> This patch appends the localversion string to the Linux kernel version.
> For example, in a git tree with uncommitted changes, the .config file
> might start as follows (but with leading hash marks):
>
> Automatically generated make config: don't edit
> Linux kernel version: 2.6.33-01836-g90a6501-dirty
> Mon Mar 1 17:05:59 2010
>
> The "-01836-g90a6501-dirty" string is added by this patch.
kbuild in linux-next already has
commit 85a256d8e0116c8f5ad276730830f5d4d473344d
Author: David Rientjes <rientjes@...gle.com>
Date: Wed Jan 13 13:01:05 2010 -0800
kbuild: improve version string logic
which results in a scripts/setlocalversion call during each build. And
with CONFIG_LOCALVERSION_AUTO, it stores exactly the string you want in
include/config/kernel.release. So we could change kconfig to read that
file instead of building the version string again. To also cover the
!CONFIG_LOCALVERSION_AUTO case, we can add a
include/config/kernel.release.full file to hold the full string each time.
Sorry for jumping in so late in the discussion, I had a bit of backlog
in mail directed to me and linux-kbuild@...r.kernel.org, let alone LKML ;).
Michal
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists