Subject: Re: What's going on here? Bad repo, no error locally?

From: "John M. Dlugosz" <[email-masked]>
Date: Tue, 21 Apr 2009 23:37:05 -0500

Bryan Donlan wrote:
> Extract the object on developer B's workstation:
> git cat-file blob <object ID>  > blob.dat
> 
> Copy it to upstream, then do:
> git hash-object -w blob.dat
> 
> If all goes well, hash-object will give you back the blob's ID, and
> the repository will fsck cleanly again.

Thanks, I was looking through the manual for that but wasn't sure how to put it together.

But, what could be wrong with B's repo that makes this happen repetetly?  I assumed it was 
network SNAFU, but after restoring the upstream repo, his push did it again.

--John