From: Nix <nix@esperi.org.uk>
To: linux@horizon.com
Cc: git@vger.kernel.org
Subject: Re: git-pull followed by git-gc often yields *much* bigger pack than git-pull alone
Date: Wed, 12 Dec 2007 22:06:17 +0000 [thread overview]
Message-ID: <87r6hrwoti.fsf@hades.wkstn.nix> (raw)
In-Reply-To: <20071212215303.29921.qmail@science.horizon.com> (linux@horizon.com's message of "12 Dec 2007 16:53:03 -0500")
On 12 Dec 2007, linux@horizon.com verbalised:
> 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
next prev parent reply other threads:[~2007-12-12 22:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-12 21:53 git-pull followed by git-gc often yields *much* bigger pack than git-pull alone linux
2007-12-12 22:06 ` Nix [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-12-12 20:47 Nix
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r6hrwoti.fsf@hades.wkstn.nix \
--to=nix@esperi.org.uk \
--cc=git@vger.kernel.org \
--cc=linux@horizon.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).