Re: SHA1 collisions found
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Feb 23, 2017, 18:38 UTC
- Message-ID
- <xmqqk28g92h7.fsf@gitster.mtv.corp.google.com>
- In-Reply-To
- <20170223181018.ns4vyosgzmuoyiva@kitenet.net>
Joey Hess <id@joeyh.name> 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?