| commit | 0b63fd6965350fd0159f7712b3582ba83cbfca25 | |
| author | Alexandr Miloslavskiy <alexandr.miloslavskiy@syntevo.com> | |
| Tue, 24 Sep 2019 10:40:29 +0000 (24 03:40 -0700) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Sat, 28 Sep 2019 04:49:47 +0000 (28 13:49 +0900) | ||
| tree | bffffaf720fb7fd834b5d825d1bfbedd8af978da | treesnapshot (tar.gz zip) |
| parent | 5fa0f5238b0cd46cfe7f6fa76c3f526ea98148d9 | commitdiff |
t0028: fix test for UTF-16-LE-BOM
According to its name, the test is designed for UTF-16-LE-BOM.
However, possibly due to copy&paste oversight, it was using UTF-32.
While the test succeeds (extra \000\000 are interpreted as NUL),
I myself had an unrelated problem which caused the test to fail.
When analyzing the failure I was quite puzzled by the fact that the
test is obviously buggy. And it seems that I'm not alone:
https://public-inbox.org/git/CAH8yC8kSakS807d4jc_BtcUJOrcVT4No37AXSz=jePxhw-o9Dg@mail.gmail.com/T/#u
Fix the test to follow its original intention.
Signed-off-by: Alexandr Miloslavskiy <alexandr.miloslavskiy@syntevo.com>
Reviewed-by: Torsten Bögershausen <tboegi@web.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
According to its name, the test is designed for UTF-16-LE-BOM.
However, possibly due to copy&paste oversight, it was using UTF-32.
While the test succeeds (extra \000\000 are interpreted as NUL),
I myself had an unrelated problem which caused the test to fail.
When analyzing the failure I was quite puzzled by the fact that the
test is obviously buggy. And it seems that I'm not alone:
https://public-inbox.org/git/CAH8yC8kSakS807d4jc_BtcUJOrcVT4No37AXSz=jePxhw-o9Dg@mail.gmail.com/T/#u
Fix the test to follow its original intention.
Signed-off-by: Alexandr Miloslavskiy <alexandr.miloslavskiy@syntevo.com>
Reviewed-by: Torsten Bögershausen <tboegi@web.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| t/t0028-working-tree-encoding.sh | diffblobblamehistory |