On Thu, May 24, 2018 at 05:25:29PM +0200, Ævar Arnfjörð Bjarmason wrote: > When I do: > > git -c fetch.fsckObjects=true clone git@xxxxxxxxxx:robbyrussell/oh-my-zsh.git > > I get: > > error: object 2b7227859263b6aabcc28355b0b994995b7148b6: zeroPaddedFilemode: contains zero-padded file modes > fatal: Error in object > fatal: index-pack failed > > The docs (https://git-scm.com/docs/git-config#git-config-fsckltmsg-idgt) > say you can override this with -c fsck.zeroPaddedFilemode = ignore, but > I see in builtin/fsck.c that just fsck_config() knows about this, and > indeed this works *after* you clone the repo when you use 'git fsck'. > > I don't have time to fix this now, but what's the best approach here? > Make all the relevant commands copy what fsck_config() is doing, or > should fsck_object() be lazily looking up this config by itself? Apparently someone reported this earlier[0]. Johannes replied: > Well, you can apparently have your cake and eat it too (see > https://git-scm.com/docs/git-config#git-config-receivefsckltmsg-idgt): > > receive.fsck.<msg-id>:: > When `receive.fsckObjects` is set to true, errors can be switched > to warnings and vice versa by configuring the `receive.fsck.<msg-id>` > setting where the `<msg-id>` is the fsck message ID and the value > is one of `error`, `warn` or `ignore`. For convenience, fsck prefixes > the error/warning with the message ID, e.g. "missingEmail: invalid > author/committer line - missing email" means that setting > `receive.fsck.missingEmail = ignore` will hide that issue. > > In your case, use receive.fsck.zeroPaddedFilemode=ignore=warn (or > =ignore). [0]https://public-inbox.org/git/alpine.DEB.2.21.1.1801042125430.32@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/ Hope this helps, Kevin.
