Thomas Ferris Nicolaisen <> writes:
> Here's what happens when I try removing some random object in my Git repo 
> (using Git 2.0.0):
> git init; git add .;git commit -m "inital"
> rm .git/objects/00/79c7f07eb4bfbc08cc21f3324e7997e0b05415
> git fsck
> Checking object directories: 100% (256/256), done.
> broken link from    tree c862bb1ab77b0d118009961c1f06d8954f98db8f
>               to    tree 0079c7f07eb4bfbc08cc21f3324e7997e0b05415
> missing tree 0079c7f07eb4bfbc08cc21f3324e7997e0b05415 
> Here I tried removing a blob instead:
> rm .git/objects/ac/9ea1b673c0bb4501415550d492474700d6bd2f
> git fsck                                                                   
> Checking object directories: 100% (256/256), done.
> missing blob ac9ea1b673c0bb4501415550d492474700d6bd2f
> So, recreated the issue, in any case. The only difference was that I found 
> the blob-to-delete by looking with ls-tree, while the first one was totally 
> random.
> I'd keep trying around a bit, see if you can find a pattern, and then ask 
> on the git-dev list.

Part of my complaint is that, of necessity, git-fsck knows what the
broken pointer is.  Indeed, it may have in its internal state all the
information needed to show the complete path from a root to the missing


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 
For more options, visit

Reply via email to