(I am using git version 1.8.3.1.) Some references for git-fsck are like this:
https://git.help.collab.net/entries/22580428-Recovering-from-repository-corruption $ git fsck --full broken link from tree 2d9263c6d23595e7cb2a21e5ebbb53655278dff8 to blob 4b9458b3786228369c63936db65827de3cc06200 missing blob 4b9458b3786228369c63936db65827de3cc06200 that is, when git-fsck reports a missing blob, it tells what object contained a link to the blob. However, when I run git-fsck, all I get is the missing blob's hash: $ git fsck --full Checking object directories: 100% (256/256), done. Checking objects: 100% (4038/4038), done. missing blob 2322b10fb1cdab6fb38a9ad1c2042285939553b6 missing blob 955c487443b7c11202aca66a0fcb0a1b29ce4645 missing blob fb67076078ca5f64f8eb6a29481f1ab4ff9bca5d missing blob a7edc7ed7a924b4e2aca62d3462fe1fdfd510d5b It seems to me that the first style is much more useful, and indeed it should be augmented so that it can show the complete traceback back to a "root" of the object structure (typically a "refs" value). Is there any way to activate the first style? Dale -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.