Re: Question about git-prune

Hi,

On Sat, 30 Jun 2007, walt wrote:

Johannes Schindelin wrote:

quoted

On Sat, 30 Jun 2007, walt wrote:

...

quoted

quoted

$git-prune
$git-fsck
dangling tree c642c018aa55d39fff061183f58062de9d8375ac
dangling commit e1341abc3759950e891822088cb0163b71b316b3
dangling commit 9f38e1ef7e7992ca490b9b419f52fb4d11efb0e4
dangling commit b82871b3c32faa8a317007f343fdf2d0ddc9954e

Probably the objects were packed.

I also tried git-prune-packed, which also did nothing AFAICT.

git-prune-packed prunes objects which are loose _and_ packed.

quoted

I do not understand why you use git-prune directly, to begin with. Why 
not use git-gc and be done with it?

It didn't exist when I started using git.  I normally don't use 
git-prune either, but in this case I was just scanning for problems 
after switching from cg-update to git-pull.

Fair enough.

git-gc did get rid of all the danglers even though git-prune didn't. 
I'll do some investigating to find out why -- that should get me more up 
to date with recent changes.

The thing you needed was actually git-repack (which is called with every 
necessary option you need from git-gc).

Basically, your objects were dangling _and_ packed. Thus you had to repack 
in order to get rid of them, but keep the others.

Ciao,
Dscho