]> git.ipfire.org Git - thirdparty/git.git/commit
t1006: stop using 0-padded timestamps
authorJeff King <peff@peff.net>
Wed, 18 Jan 2023 20:35:52 +0000 (15:35 -0500)
committerJunio C Hamano <gitster@pobox.com>
Wed, 18 Jan 2023 20:59:44 +0000 (12:59 -0800)
commit61cc4be7ec21f0217abacc396287ca12c68e923d
tree28bad13f284974022471cc754ec4879aee1367d3
parent6e2646075c456f2bd3dfe6afd7d72316174b02ed
t1006: stop using 0-padded timestamps

The fake objects in t1006 use dummy timestamps like "0000000000 +0000".
While this does make them look more like normal timestamps (which,
unless it is 1970, have many digits), it actually violates our fsck
checks, which complain about zero-padded timestamps.

This doesn't currently break anything, but let's future-proof our tests
against a version of hash-object which is a little more careful about
its input. We don't actually care about the exact values here (and in
fact, the helper functions in this script end up removing the timestamps
anyway, so we don't even have to adjust other parts of the tests).

Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
t/t1006-cat-file.sh