threads / discuss / 10236

Lots of loose objects

Subject: Lots of loose objects

## tl;dr

2 messages between Oct 10, 2007 and Oct 10, 2007.

replies: 1people: 2as markdown or json

David Kågedal· Oct 10, 2007, 19:13 UTC · lore

I hade a tree that made git-gui complain that I had too many loose objects every time I started it (3072 to be precise). Letting git-gui compress it for me didn't help. Neither did git-gc, even with the --aggressive flag.

I noticed that I had a lot of loose files in .git/objects, and suddenly I remembered that there was a command called "git prune". Finally I was able to get rid of those loose objects.

The problem here is probably mostly that I couldn't get any help from git-gui or git-gc. git-gui claimed it would fix the problem for me, but failed. git-gc didn't mention that it left a bunch of files untouched.

-- 
David Kågedal

Johannes Schindelin· Oct 10, 2007, 19:37 UTC · re: David Kågedal · lore

Re: Lots of loose objects

Hi,

On Wed, 10 Oct 2007, David Kågedal wrote:

Show 8 quoted lines

> I hade a tree that made git-gui complain that I had too many loose
> objects every time I started it (3072 to be precise).  Letting git-gui
> compress it for me didn't help.  Neither did git-gc, even with the
> --aggressive flag.
> 
> I noticed that I had a lot of loose files in .git/objects, and
> suddenly I remembered that there was a command called "git
> prune". Finally I was able to get rid of those loose objects.

Probably git-gui should check again, after the compacting stage, how many loose objects there are, and suggest to run git prune after a sufficiently terrifying warning message ("Should I prune unreferenced objects? (DON'T do this if you share objects between repositories!) Yes / No").

Ciao, Dscho