From: John Keeping <john@keeping.me.uk>
To: Duy Nguyen <pclouds@gmail.com>
Cc: "Дилян Палаузов" <dilyan.palauzov@aegee.org>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: git pull & git gc
Date: Wed, 18 Mar 2015 14:58:15 +0000 [thread overview]
Message-ID: <20150318145815.GN1369@serenity.lan> (raw)
In-Reply-To: <CACsJy8DCdF1YmfFF1aCuhMJ0v4+FW7EkDiwBnBF2OFhE=kcbFg@mail.gmail.com>
On Wed, Mar 18, 2015 at 09:41:59PM +0700, Duy Nguyen wrote:
> On Wed, Mar 18, 2015 at 9:33 PM, Duy Nguyen <pclouds@gmail.com> wrote:
> > If not, I made some mistake in analyzing this and we'll start again.
>
> I did make one mistake, the first "gc" should have reduced the number
> of loose objects to zero. Why didn't it.? I'll come back to this
> tomorrow if nobody finds out first :)
Most likely they are not referenced by anything but are younger than 2
weeks.
I saw a similar issue with automatic gc triggering after every operation
when I did something equivalent to:
git add <lots of files>
git commit
git reset --hard HEAD^
which creates a log of unreachable objects which are not old enough to
be pruned.
next prev parent reply other threads:[~2015-03-18 15:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 13:53 git pull & git gc Дилян Палаузов
2015-03-18 14:16 ` Duy Nguyen
2015-03-18 14:23 ` Дилян Палаузов
2015-03-18 14:33 ` Duy Nguyen
2015-03-18 14:41 ` Duy Nguyen
2015-03-18 14:58 ` John Keeping [this message]
2015-03-18 21:04 ` Jeff King
2015-03-19 0:31 ` Duy Nguyen
2015-03-19 1:27 ` Jeff King
2015-03-19 2:01 ` Mike Hommey
2015-03-19 4:14 ` Jeff King
2015-03-19 4:26 ` Mike Hommey
2015-03-19 2:27 ` Junio C Hamano
2015-03-19 4:09 ` Jeff King
2015-03-19 4:15 ` Duy Nguyen
2015-03-19 4:20 ` Jeff King
2015-03-19 4:29 ` Duy Nguyen
2015-03-19 4:34 ` Jeff King
2015-03-19 9:47 ` Duy Nguyen
2015-03-18 14:48 ` Дилян Палаузов
2015-03-18 21:07 ` Jeff King
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=20150318145815.GN1369@serenity.lan \
--to=john@keeping.me.uk \
--cc=dilyan.palauzov@aegee.org \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.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).