Git repo is corrupt

[kevinburkeshyp]

It appears that some of the objects in the git tree added a zero-padded file mode, there's a little more info about this here: http://comments.gmane.org/gmane.comp.version-control.git/143288, http://stackoverflow.com/questions/15598465/should-i-worry-about-git-fsck-warning-contains-zero-padded-file-modes, https://www.perforce.com/blog/150109/git-out-vulnerability-out-fire

You can reproduce this by running "git fsck"

$ git fsck
Checking object directories: 100% (256/256), done.
warning in tree b3f0a2c652b54c963ea52ec4bb52897598445888: zeroPaddedFilemode: contains zero-padded file modes
warning in tree 2903c531572202f28d16cd34ceaf507f62ae72b3: zeroPaddedFilemode: contains zero-padded file modes
warning in tree 0d52bf9c60888d16bdb2c2e318548d8afe6d122f: zeroPaddedFilemode: contains zero-padded file modes
warning in tree 0f88fdf9d00afc38bcaf5277bbffbe6529645c90: zeroPaddedFilemode: contains zero-padded file modes
warning in tree 3d5b35d4d07b5c3900ed7cffd197eefd9a4ec43f: zeroPaddedFilemode: contains zero-padded file modes
warning in tree a4c15f42e32f5af64621fcbd49802bf353c5e390: zeroPaddedFilemode: contains zero-padded file modes
Checking objects: 100% (1032/1032), done.
dangling blob 42624ed50312acba20d4228d6ac486ac38d1146d
dangling blob 85dd0c870fe712fa8b9f25aeb81ec56d7ef461b9

I'm not sure whether you want to take on the solution, which would probably involve rewriting a significant amount of the history.

[moshen]

Ug... Thanks for letting us know. This may take a bit to coordinate a the fix.