"Eric W. Biederman" <ebied...@xmission.com> wrote: > > Recently I ran git --git-dir=lkml/git/1.git fsck > and it reported: > > warning in commit 299dbd50b6995c6debe2275f0df984ce697fb4cc: nulInCommit: > > NULL byte inthe commit object body > > Which I found quite scary. Nulls in the wrong place have a bad tendency > to make programs misbehave.
Thanks. In this case, it's a bit weird for fast-import to accept this... > + # Mime decoding can create nulls replace them with spaces to protect git > + $subject =~ s/\0/ /; \0 could appear more than once, so it needs a 'g', at least. I squashed in a change to use "tr/\0/ /" instead (tr// should be faster) -- unsubscribe: meta+unsubscr...@public-inbox.org archive: https://public-inbox.org/meta/
