One of our guys pushed a commit that seems to be whole and working on his computer. Since then, none of the other computers is able to fetch changes from the remote repository. The error that everyone is getting is:
git.exe fetch -v --progress "origin"
POST git-upload-pack (gzip 1407 to 775 bytes)
remote: error: Could not read a75720ce47ae8dcc1d0b4c09fcb7d6f70efa390b
remote: fatal: revision walk setup failed
remote: aborting due to possible repository corruption on the remote side.
fatal: protocol error: bad pack header
git did not exit cleanly (exit code 128) (14368 ms @ 26/10/2014 11:49:05)
The SHA (a75720...) that can't be read is the SHA of said commit.
We've tried various things, but nothing seems to work. Running git fsck does not show the commit as dangling, and in the remote server, no branch is pointing to the commit.
Recovering data from the commit is not a priority, but getting the system working again is.
Any suggestions as to how to delete/fix the broken commit? Help would be greatly appreciated.
Thanks!