From: Theodore Tso <tytso@mit.edu>
Date: Mon, 15 Dec 2008 19:38:37 GMT
Subject: Re: "git gc" doesn't seem to remove loose objects any more
Message-ID: <20081215193837.GB11502@mit.edu>
In-Reply-To: <m3vdtlcqp6.fsf@localhost.localdomain>

On Mon, Dec 15, 2008 at 09:07:39AM -0800, Jakub Narebski wrote:
> 
> There was an idea to have "git gc --prune" run "git prune"
> unconditionally, i.e. without grace period for dangling loose objects.
> 

That doesn't help that much, since (temporarily) you still need all of
the disk space for the exploded, unpacked objects.  As Brandon Casey
pointed out, the key is "git repack -a -d -l" vs "git repack -A -d
-l".  If there is going to be a git-gc option, it would need to change
the options sent to git-repack.  Or, I suppose the answer is to tell
people who run into this problem use a plumbing command, manually.
The question is how common is the use case of needing to gc a
repository like linux-next, I suppose.

							- Ted