Re: bug in git-fsck-cache?

From: Junio C Hamano <junkio@cox.net>
Date: Sep 1, 2005, 02:21 UTC
Message-ID: <7vacix5y0h.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <20050901120226.54547107.git@ozlabs.org>

Stephen Rothwell <git@ozlabs.org> writes:

Show 15 quoted lines

>> Stephen Rothwell <git@ozlabs.org> writes:
>> 
>> > The commit c594adad5653491813959277fb87a2fef54c4e05 is shown as
>> > "connected" (in Linus' tree, not one of my patches) by gitk, so I am happy
>> > that git prune did not get rid of it, but why does fsck-cache report it as
>> > dangling?
>> 
>> Hmph.  You ran fsck-cache by hand without --full (i.e. you told
>> it not to worry about objects already in packs); 'git prune'
>> runs it with '--full' to do the full connectivity analysis.  I
>> think that's where the difference comes from.
>
> ok, with '--full' nothing gets reported as dangling.  That commit is not
> in a pack, but is in an object directory referenced through
> objects/info/alternates.

Ahh. Yes, it is the same thing. I said "not in the pack", but I should have said "exists locally unpacked".