All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Stephens <bruce.stephens@isode.com>
To: git@vger.kernel.org
Subject: "git gc" doesn't seem to remove loose objects any more
Date: Mon, 15 Dec 2008 12:52:34 +0000	[thread overview]
Message-ID: <808wqhzjl9.fsf@tiny.isode.net> (raw)

I couldn't see a test for this, but perhaps I'm just missing it?

    brs% git count-objects
    161 objects, 1552 kilobytes
    brs% git gc
    Counting objects: 80621, done.
    Compressing objects: 100% (22372/22372), done.
    Writing objects: 100% (80621/80621), done.
    Total 80621 (delta 57160), reused 80305 (delta 56884)
    brs% git count-objects
    207 objects, 2048 kilobytes


And I see lots of directories under .git/objects which confirms
things.

I don't think I've changed any relevant configuration.

This is with 8befc50c49e8a271fd3cd7fb34258fe88d1dfcad (also whatever
version I used before, erm, probably
de0db422782ddaf7754ac5b03fdc6dc5de1a9ae4), and possibly earlier
versions---I've just started noticing now that the number of loose
objects has started causing git gui to complain.

(Hmm, I note that git gui reports a larger number of loose objects
than git count-objects.  Ah, OK, it really is just an approximation,
so no surprise.)

             reply	other threads:[~2008-12-15 12:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-15 12:52 Bruce Stephens [this message]
2008-12-15 13:38 ` "git gc" doesn't seem to remove loose objects any more Mikael Magnusson
2008-12-15 14:08   ` Bruce Stephens
2008-12-15 14:08   ` Björn Steinbrink
2008-12-15 15:56     ` Theodore Tso
2008-12-15 16:12       ` Mark Brown
2008-12-15 16:59         ` Johan Herland
2008-12-15 16:59         ` Mikael Magnusson
2008-12-15 17:07       ` Jakub Narebski
2008-12-15 19:38         ` Theodore Tso
2008-12-15 17:11       ` Brandon Casey
2008-12-15 17:38       ` [PATCH] objects to be pruned immediately don't have to be loosened Nicolas Pitre

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=808wqhzjl9.fsf@tiny.isode.net \
    --to=bruce.stephens@isode.com \
    --cc=git@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.