From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: James Cloos <cloos@jhcloos.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, zippel@linux-m68k.org,
mingo@elte.hu, akpm@linux-foundation.org
Subject: Re: [PATCH RFC] kconfig: place git SHA1 in .config output if in git tree
Date: Mon, 1 Mar 2010 17:20:55 -0800 [thread overview]
Message-ID: <20100302012055.GK6758@linux.vnet.ibm.com> (raw)
In-Reply-To: <m3r5o34vnp.fsf@lugabout.jhcloos.org>
On Mon, Mar 01, 2010 at 03:46:26PM -0500, James Cloos wrote:
> >>>>> "Paul" == Paul E McKenney <paulmck@linux.vnet.ibm.com> writes:
>
> Paul> Agreed! The "-dirty" modifier for the case of changes not yet
> Paul> checked into git looks especially helpful.
>
> Except that the script calls »git update-index --refresh --unmerged«
> and »git diff-index --name-only HEAD«, both of which are painfully
> slow and resource intensive.
>
> I'd hate to have that run every time I make a kernel.
Good point... Should we have an environment variable that controls this
behavior?
Thanx, Paul
next prev parent reply other threads:[~2010-03-02 1:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-01 4:22 [PATCH RFC] kconfig: place git SHA1 in .config output if in git tree Paul E. McKenney
2010-03-01 8:34 ` Ingo Molnar
2010-03-01 9:42 ` Frans Pop
2010-03-01 10:10 ` Geert Uytterhoeven
2010-03-01 16:27 ` Paul E. McKenney
2010-03-01 16:53 ` Frans Pop
2010-03-01 18:16 ` Paul E. McKenney
2010-03-01 20:29 ` Frans Pop
2010-03-02 1:16 ` Paul E. McKenney
2010-03-02 15:19 ` Frans Pop
2010-03-03 0:01 ` Paul E. McKenney
2010-03-03 0:42 ` Frans Pop
2010-03-03 2:19 ` Paul E. McKenney
2010-03-01 16:22 ` Linus Torvalds
2010-03-01 16:48 ` Paul E. McKenney
2010-03-01 20:46 ` James Cloos
2010-03-02 1:20 ` Paul E. McKenney [this message]
2010-03-02 1:53 ` James Cloos
2010-03-02 5:21 ` Paul E. McKenney
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=20100302012055.GK6758@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=cloos@jhcloos.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.