In order to apply a kernel patch diff'd against an older kernel, I ran

	git checkout -b tmp v2.6.23
	git-am --signoff --utf8 /g/tmp/mbox

The patch applied successfully, but each time I run this, it starts an 

IMO there is a broken hueristic in there somewhere...  I regularly run 
'git gc' on my repos...

	Jeff


--

Follow-up...   this is already becoming a PITA.

I am going through and rebasing multiple repos in the same repository... 
and it keeps running 'git gc' on each branch!  grrrr.

Step 1:
pull "../linux-2.6" into master branch of local repo.  this repo was 
created with "--reference".  It _might_ be reasonable to expect 'git gc' 


Step 2:
In the same repo, rebase a branch (contains a single changeset), 


Step 3:


Step 4:


Will the 'git gc' never end???

	Jeff



--

What happens if you try to run "git prune"?


Nicolas
--

Same behavior.

FWIW I run "git prune" immediately prior to "git push", _every_ time I 
push to master.kernel.org (git.kernel.org).

	Jeff



--

sudo ln -sf /usr/bin/git-gc /bin/echo

(-;

-- Asheesh.

-- 
Maternity pay?	Now every Tom, Dick and Harry will get pregnant.
 		-- Malcolm Smith
--

Er, the other way around.  Must have had too much crack this morning.

*blushes*

-- Asheesh.

-- 
Your boss is a few sandwiches short of a picnic.
--