Re: git fsck messages - what to do about it?

From: Wolfgang Denk <wd@denx.de>
Date: Sep 16, 2005, 11:03 UTC
Message-ID: <20050916110310.90115352B7B@atlas.denx.de>
In-Reply-To: <tnx3bo59tm8.fsf@arm.com>

In message <tnx3bo59tm8.fsf@arm.com> you wrote:

Show 21 quoted lines

>
> > -> git-fsck-cache --unreachable $(cat .git/HEAD .git/refs/heads/*)
> > unreachable commit 08cf4121ad704faa5ae7c7ae7b3dca4476ef2770
> > unreachable tree 29a4c18afd958cc6cee938f0fe7fa59764418097
> > unreachable tree 3b722a7278e02b272ddc8aefbc7be22703d8a94f
> > unreachable tree 4ebc50d240d99b4236952d13d5044691f9078e3c
> > unreachable tree 63af5944e130b449338cc907ee77c51f4a69e339
> > unreachable tree 79c9a6bb02a80df15c7d829bdac0901f88c5e301
> > unreachable blob 85dcf4b5c4c0f6833cd63fa1d0fd29ef250162af
> > unreachable commit c1b779fbce762c970e3ace4332bb6ddc0de65e61
> > unreachable blob d70d1d44f12db7b2a3976c2a5313c90568a62c25
> > unreachable commit e1bcd2a5d53bceef2679737474487e32d87e7f2c
> >
> > I have to admit that I don't know what to do next...
> >
> > a) I understand that these  messages  are  indications  of  problems,
> >    right? What can I do to clean this up?
> >
> > b) Is there any way to find out what I did wrong in the first place?
> 
> Did you use StGIT on your tree? StGIT can leave unreachable

No, I did not. I *think* these unreachable commits resulted from "git resolve"s which resulted in merge conflicts, which I resolved manually. After this, I ran "git commit" manually, but probably I did something wrong. I just don't understand what this might have been...

> objects. Otherwise, git-prune should remove them.

Ummm.... I hesitate to do this before understanding where these messages come from and what sort of data is affected.

> Note that if you use StGIT, git-prune will also remove the commit

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Remember that Beethoven wrote his first symphony in C ...