Re: git-push of new, tiny branch doing more work than necessary?

From: Andy Whitcroft <apw@shadowen.org>
Date: Sep 22, 2006, 07:40 UTC
Message-ID: <45139379.4040602@shadowen.org>
In-Reply-To: <Pine.LNX.4.63.0609220031570.19042@wbgn013.biozentrum.uni-wuerzburg.de>

Johannes Schindelin wrote:

Show 21 quoted lines

> Hi,
> 
> On Thu, 21 Sep 2006, Carl Worth wrote:
> 
>> I've run through something quite like the following scenario a few
>> times lately:
>>
>> 	git pull origin
>> 	git checkout -b experiment
>> 	# hack a file or two
>> 	git commit -a -m "new experiment"
>> 	git push origin experiment
>>
>> What I expect at this point is for git to push the few newly created
>> objects out to the repository. Instead it talks about generating,
>> deltifying, transferring, and unpacking thousands of objects (see
>> below).
> 
> I experienced something like this, too, but did not have the time to debug 
> it. But alas, some time (I think last week) it started working as expected 
> again.

I hope this started working again because we fixed it this time. Two bugs were fixed in this area. First any branch names over about 40 characters in length were being ignored completely due to a validation bug. Second in an attempt to ensure we didn't bust the 900 entry command line limit for rev-list we were restricting ourselves to 16 remote refs as possible bases. master now has these changes in it and I am no longer seeing this behavior.

> 
>> git version 1.4.2.rc2.gef1d9
> 
> Please try a more recent version (yours is from Jul 27).

-apw