[Question] Git recovery with HEAD commit broken

I am not a developer for git, but i am a regular user with git, i came the following problem: A power off cause my top commit broken, and then git branch/log/reflog..etc won't work. I do a hack that i change the HEAD commit to the one that i can make sure is right, and then i do: # git reset

Re: [Question] Git recovery with HEAD commit broken

Shilong Wang wangshilong1...@gmail.com writes: A power off cause my top commit broken, and then git branch/log/reflog..etc won't work. With a bit of luck, the reflog actually contain useful information. Look at .git/logs/HEAD (or refs/heads/* instead of HEAD for branches' reflog). It's a

Re: [Question] Git recovery with HEAD commit broken

Matthieu Moy wrote: Not as far as I know. But git fsck has a --lost-found option that can help recovering unreachable (dangling) commits. You may have a look at http://hackage.haskell.org/package/git-repair but I do not think it would solve your particular case. Well, let's find out.. I

Re: [Question] Git recovery with HEAD commit broken

Joey Hess wrote: [2] A particularly annoying one is that git branch -d cannot be used to remove a branch that is directly pointing to a corrupted commit! It's generally considered okay for everyday commands like git branch -d not to cope well with corrupted repositories, but we try to keep