Joey Hess <id@xxxxxxxxxx> writes:
> For example, git fsck does warn about a commit message with opaque
> data hidden after a NUL. But, git show/merge/pull give no indication
> that something funky is going on when working with such commits.
Would
$ git config transfer.fsckobjects true
help?