Community
Participate
Working Groups
Tree objects whose subtree pointers use a leading '0' in the mode field must be permitted. Currently these are being rejected. But a discussion on the Git mailing list [1] has determined that there are at least 16 such trees in the official Linux kernel history, and GitHub has estimated at least 100 customer projects contain the same problem. [1] http://thread.gmane.org/gmane.comp.version-control.git/143288 [2] http://support.github.com/discussions/repos/2566-strange-warning-from-fsck-and-github-repo-using-too-much-diskspace
FWIW, it appears that the kernel is clean and this problem only exists in repositories from GitHub [1]. [1] http://article.gmane.org/gmane.comp.version-control.git/143352
This issue is resulting in serious headaches for us. Our Webdesign team had been using the GitHub online Editor for some time and therefore nearly all of our repositories have some commits with leading '0'. Completely rewriting active repositories with a bout a dozen developers looks like a PIA so it would be very helpful if JGit (and in our case gerrit) would be able to handle this "extension" of the format created by GitHub.
https://git.eclipse.org/r/23224
Supported now by setting fsck.allowLeadingZeroFileMode to true.