Re: git clone sending unneeded objects
- From
Jason Merrill <jason@redhat.com>
- Date
- Sep 26, 2009, 13:33 UTC
- Message-ID
- <4ABE1818.6010007@redhat.com>
- In-Reply-To
- <4ABD9C2C.60800@redhat.com>
On 09/26/2009 12:44 AM, Jason Merrill wrote:
> git config remote.origin.fetch 'refs/remotes/*:refs/remotes/origin/*' > git fetch
git count-objects -v before:
count: 44 size: 1768 in-pack: 1399509 packs: 1 size-pack: 600456 prune-packable: 0 garbage: 0
and after (transferred 278MB):
count: 44 size: 1768 in-pack: 1947339 packs: 2 size-pack: 1178408 prune-packable: 8 garbage: 0
and then after git gc --prune=now:
count: 0 size: 0 in-pack: 1399613 packs: 1 size-pack: 839900 prune-packable: 0 garbage: 0
So I only actually needed 104 more objects, but fetch wasn't clever enough to see that, and my new pack is much less efficient.
I've run into the same issue using alternates to set up multiple working directories for different branches; if the alternate directory isn't completely up-to-date, fetch wants to pull down lots of data again rather than use what I have and only fetch the last one or two commits.
Jason