Zero-padded file modes

[sgraf812]

Running git fsck yields the following output for me:

Checking object directories: 100% (256/256), done.
warning in tree 28364970824df3bd81620881276330a2e941a6c1: zeroPaddedFilemode: contains zero-padded file modes
Checking objects: 100% (6294/6294), done.

Unfortunately this means I can't locally push a fork of this repo to a private GitLab instance, because that instance seems to error out when encountering this.

Just posting this here so that you are aware. There seems to be no solution other than to rewrite history (thus changing all commit SHAs) or for me to prompt my GitLab hoster to omit that check.

Related GitLab issue: https://gitlab.com/gitlab-org/gitlab-ce/issues/22095, so it's probably 'their fault'.

[tobami]

I was not aware of this issue. Rewriting history for a project that has been around for so long is not a realistic option, so we'll have to wait for Gitlab to fix that!

[mwatts15]

This issue can probably be closed as wontfix