summaryrefslogtreecommitdiff
path: root/gitk-git/gitk
diff options
context:
space:
mode:
authorLibravatar Kevin Daudt <me@ikke.info>2019-02-11 22:38:18 +0100
committerLibravatar Junio C Hamano <gitster@pobox.com>2019-02-11 14:46:36 -0800
commit99e9ab54aba21b8fa368f20e6b3585d95b1c4d37 (patch)
treed4029e5af1e692e576ed616e6b9c3f80fbbab895 /gitk-git/gitk
parentGit 2.18.1 (diff)
downloadtgif-99e9ab54aba21b8fa368f20e6b3585d95b1c4d37.tar.xz
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>
Diffstat (limited to 'gitk-git/gitk')
0 files changed, 0 insertions, 0 deletions