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

From: Carl Worth <cworth@cworth.org>
Date: 2006-09-22 08:29:04
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).

Shouldn't the same WANT/HAVE hand shaking that makes git-fetch
efficient be doing something similar here? Or am I just doing
something wrong?

-Carl

$ git --version
git version 1.4.2.rc2.gef1d9
$ git push cworth 8379
updating 'refs/heads/8379'
  from 0000000000000000000000000000000000000000
  to   44379202da96faf632b73cdcdd6c0a74fb4b54f4
Generating pack...
Done counting 4900 objects.
Result has 4622 objects.
Deltifying 4622 objects.
 100% (4622/4622) done
Unpacking 4622 objects
Total 4622, written 4622 (delta 3411), reused 1259 (delta 946)
refs/heads/8379: 0000000000000000000000000000000000000000 ->
44379202da96faf632b73cdcdd6c0a74fb4b54f4

-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Received on Fri Sep 22 08:29:23 2006

This archive was generated by hypermail 2.1.8 : 2006-09-22 08:30:11 EST