From: Junio C Hamano <gitster@pobox.com>
Date: Wed, 22 Apr 2009 05:06:54 GMT
Subject: Re: What's going on here? Bad repo, no error locally?
Message-ID: <7vws9d46q9.fsf@gitster.siamese.dyndns.org>
In-Reply-To: <450196A1AAAE4B42A00A8B27A59278E70ACE053E@EXCHANGE.trad.tradestation.com>

"John Dlugosz" <JDlugosz@TradeStation.com> writes:

> Developer B runs git fsck --full, gets no errors but one dangling blob.
> Does a push.  No errors.
> Now, on the upstream repo, I run fsck, and find a bunch of danglings (as
> always) and a missing blob.
> Any fetch from that repo will fail, due to that missing blob.
>
> What's going on?  How can I fix his local repository, other than...

It sounds like there is nothing to fix in "his local repository"; the
error is in your "upstream repo".

The dangling objects can happen if you push over dumb transport and
interrupt in the middle, or you force a push of a rewound branch, so it
does not necessarily indicate any errors, but a missing object is always
an error.