Re: git-pull followed by git-gc often yields much bigger pack than git-pull alone

From: Nix <nix@esperi.org.uk>
Date: Dec 12, 2007, 22:06 UTC
Message-ID: <87r6hrwoti.fsf@hades.wkstn.nix>
In-Reply-To: <20071212215303.29921.qmail@science.horizon.com>

On 12 Dec 2007, linux@horizon.com verbalised:

Show 10 quoted lines

> Pre-gc:
>> -r--r--r-- 1 compiler hackers   12080 2007-12-12 20:35 pack-f534c957f3ee7f3f1046dee0081fcc315d9698bb.idx
>> -r--r--r-- 1 compiler hackers  678643 2007-12-12 20:35 pack-f534c957f3ee7f3f1046dee0081fcc315d9698bb.pack
>
> Post-gc:
>> -r--r--r-- 1 compiler hackers   20912 2007-12-12 20:36 pack-5145ce9770077cee99795fc21cfcc6ea30eb6d47.idx
>> -r--r--r-- 1 compiler hackers 1144055 2007-12-12 20:36 pack-5145ce9770077cee99795fc21cfcc6ea30eb6d47.pack
>
> The fact that the index file has grown so much indicates that it's sucking in a bunch of
> extra objects from the .keep pack, and you're seeing the duplication.

I thought it had to be doing that (hence the increase in object counts given by the git-gc runs), but wasn't sure if this behaviour was intentional.

> I'm not sure how that's happening, though.  I thought the --local flag to git-pack-objects told
> it not to do that.

This isn't true if alternates are in use, but this repo is alternate-free.

-- 
`The rest is a tale of post and counter-post.' --- Ian Rawlings
                                                   describes USENET

Re: git-pull followed by git-gc often yields *much* bigger pack than git-pull alone

Re: git-pull followed by git-gc often yields much bigger pack than git-pull alone