From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Mike Galbraith <efault@gmx.de>
Cc: linux-kernel@vger.kernel.org, zippel@linux-m68k.org,
mingo@elte.hu, akpm@linux-foundation.org,
torvalds@linux-foundation.org, geert@linux-m68k.org,
elendil@planet.nl, cloos@jhcloos.com
Subject: Re: [PATCH] v3 kconfig: place git SHA1 in .config output if in SCM
Date: Fri, 5 Mar 2010 04:57:31 -0800 [thread overview]
Message-ID: <20100305125730.GA6764@linux.vnet.ibm.com> (raw)
In-Reply-To: <1267769448.6392.17.camel@marge.simson.net>
On Fri, Mar 05, 2010 at 07:10:48AM +0100, Mike Galbraith wrote:
> On Thu, 2010-03-04 at 18:54 -0800, 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.
>
> I really like this. This gives me the advantages of non-volatile build
> info without the mess that makes if it's appended to file names/paths.
Glad you like it! ;-)
> -Mike
>
> Eventually someone will make bisect stop stepping on random kernels, and
> generally making a mess, and life will be grand ;-)
Heck, I don't even know how bisect deals with merges. ;-)
Thanx, Paul
prev parent reply other threads:[~2010-03-05 12:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-05 2:54 [PATCH] v3 kconfig: place git SHA1 in .config output if in SCM Paul E. McKenney
2010-03-05 3:43 ` Frans Pop
2010-03-05 5:20 ` Paul E. McKenney
2010-03-05 17:18 ` Frans Pop
2010-03-05 20:10 ` Paul E. McKenney
2010-03-05 20:31 ` Frans Pop
2010-03-05 20:49 ` Paul E. McKenney
2010-03-05 6:10 ` Mike Galbraith
2010-03-05 12:57 ` Paul E. McKenney [this message]
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=20100305125730.GA6764@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=cloos@jhcloos.com \
--cc=efault@gmx.de \
--cc=elendil@planet.nl \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.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