On Tue, Apr 21, 2009 at 8:18 PM, John Dlugosz <JDlugosz@xxxxxxxxxxxxxxxx> wrote: > 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 blow it > away and start over, and copy his current files over and rebuild the few > commits of interest? 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. -- 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