summaryrefslogtreecommitdiff
path: root/Documentation/i18n.txt
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <gitster@pobox.com>2016-04-14 10:58:22 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2016-05-10 10:02:06 -0700
commit6d2d780f6359df424a625a51f09da80ab6dc1ef8 (patch)
treec9d93dba9b6fccbc3adb20ceaa3b590a897e855b /Documentation/i18n.txt
parentfsck_commit_buffer(): do not special case the last validation (diff)
downloadtgif-6d2d780f6359df424a625a51f09da80ab6dc1ef8.tar.xz
fsck: detect and warn a commit with embedded NUL
Even though a Git commit object is designed to be capable of storing any binary data as its payload, in practice people use it to describe the changes in textual form, and tools like "git log" are designed to treat the payload as text. Detect and warn when we see any commit object with a NUL byte in it. Note that a NUL byte in the header part is already detected as a grave error. This change is purely about the message part. Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/i18n.txt')
0 files changed, 0 insertions, 0 deletions