On Wed, Apr 22, 2009 at 12:37 AM, John M. Dlugosz <ngnr63q02@xxxxxxxxxxxxxx> wrote: > 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. Theoretically, this should never happen :) Are you accessing the repo directly through a file share, or through a git-daemon connection? If the former, could something like a virus scanner be deleting loose objects, perhaps? -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html