| commit | 99e9ab54aba21b8fa368f20e6b3585d95b1c4d37 | |
| author | Kevin Daudt <me@ikke.info> | |
| Mon, 11 Feb 2019 21:38:18 +0000 (11 22:38 +0100) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Mon, 11 Feb 2019 22:46:36 +0000 (11 14:46 -0800) | ||
| tree | d4029e5af1e692e576ed616e6b9c3f80fbbab895 | treesnapshot (tar.gz zip) |
| parent | 268fbcd172cdb306e8a3e7143cc16677c963d6cd | commitdiff |
t0028: fix wrong octal values for BOM in setup
The setup code uses octal values with printf to generate a BOM for
UTF-16/32 BE/LE. It specifically uses '\777' to emit a 0xff byte. This
relies on the fact that most shells truncate the value above 0o377.
Ash however interprets '\777' as '\77' + a literal '7', resulting in an
invalid BOM.
Fix this by using the proper value of 0xff: '\377'.
Signed-off-by: Kevin Daudt <me@ikke.info>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
The setup code uses octal values with printf to generate a BOM for
UTF-16/32 BE/LE. It specifically uses '\777' to emit a 0xff byte. This
relies on the fact that most shells truncate the value above 0o377.
Ash however interprets '\777' as '\77' + a literal '7', resulting in an
invalid BOM.
Fix this by using the proper value of 0xff: '\377'.
Signed-off-by: Kevin Daudt <me@ikke.info>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| t/t0028-working-tree-encoding.sh | diffblobblamehistory |