Prev: [PATCH 4/7] xen: The entrance for PV extension of HVM
Next: linux-next: build warning after merge of the acpi tree
From: James Cloos on 1 Mar 2010 21:30
>>>>> "Paul" == Paul E McKenney <paulmck(a)linux.vnet.ibm.com> writes:

Paul> Agreed! The "-dirty" modifier for the case of changes not yet
Paul> checked into git looks especially helpful.

JimC> Except that the script calls »git update-index --refresh --unmerged«
JimC> and »git diff-index --name-only HEAD«, both of which are painfully
JimC> slow and resource intensive.

JimC> I'd hate to have that run every time I make a kernel.

Paul> Good point... Should we have an environment variable that controls
Paul> this behavior?

I wouldn't mind the intial idea: just the abbreviated top of three hash.

I was, next, going to write that CONFIG_LOCALVERSION_AUTO already exists
for that, but LOCALVERSION_AUTO calls scripts/setlocalversion these days
and that is what I'd prefer to avoid. [SIGH]

Shows how long it has been since I last used it. I stopped using it
when I was maintaining my .config in git. Now I maintain .config in a
separate git repo, for the express purpose of avoiding a merge (rather
than a fast forward) when I run git pull. Something that a local edit
of scripts/setlocalversion will, of course, prevent.

Anyone up for a CONFIG_LOCALVERSION_AUTO_DO_NOT_BOTHER_WITH_DIRTY? ☺

-JimC
--
James Cloos <cloos(a)jhcloos.com> OpenPGP: 1024D/ED7DAEA6
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: [PATCH 4/7] xen: The entrance for PV extension of HVM
Next: linux-next: build warning after merge of the acpi tree