Re: fsck-object --standalone got errors

From: Junio C Hamano <junkio@cox.net>
Date: Mar 9, 2006, 03:17 UTC
Message-ID: <7v7j74fgsh.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <440F945C.2010401@brocade.com>

Ming Lei <mlei@brocade.com> writes:

> I have a repository created by GIT itself(not cognito, etc). It has
> branches called base, master and origin. When I did git-fsck-objects
> --full there is nothing shown, but when I did git-fsck-objects
> --standalone, it displayed following:

That is really an artifact from a distant past. Please do not worry about that error -- as long as --full does not see anything long, there is nothing wrong with your repository.

The fsck-object command (back then it was called fsck-cache) complained if objects referred to by files in .git/refs/ or objects stored in files under .git/objects/??/ are not found as stand-alone SHA1 files (i.e. found in alternate object pools or packed archives stored under .git/objects/pack). Back then, packs and alternates were curiosity and having everything as loose objects were the norm.

When we adjusted the behaviour of fsck-cache to consider objects found in packs are OK, we introduced the --standalone flag as a backward compatibility measure.

It still correctly checks if your repository is complete and consists only of loose objects, so in that sense it is doing the "right" thing, but checking that is pointless these days. We probably should remove that flag.