summaryrefslogtreecommitdiff
path: root/builtin/am.c
diff options
context:
space:
mode:
authorJohannes Schindelin <johannes.schindelin@gmx.de>2017-04-26 19:29:42 (GMT)
committerJunio C Hamano <gitster@pobox.com>2017-04-27 04:07:40 (GMT)
commit28f4aee3fb1a45ebcda8ff84f94d6d2d0053f887 (patch)
tree764bf7af33f9faee1dc1d7083a1d9885a6f218bd /builtin/am.c
parent1e65a982da0e9dd4eac440e82392a8b7c72b3def (diff)
downloadgit-28f4aee3fb1a45ebcda8ff84f94d6d2d0053f887.zip
git-28f4aee3fb1a45ebcda8ff84f94d6d2d0053f887.tar.gz
git-28f4aee3fb1a45ebcda8ff84f94d6d2d0053f887.tar.bz2
use uintmax_t for timestamps
Previously, we used `unsigned long` for timestamps. This was only a good choice on Linux, where we know implicitly that `unsigned long` is what is used for `time_t`. However, we want to use a different data type for timestamps for two reasons: - there is nothing that says that `unsigned long` should be the same data type as `time_t`, and indeed, on 64-bit Windows for example, it is not: `unsigned long` is 32-bit but `time_t` is 64-bit. - even on 32-bit Linux, where `unsigned long` (and thereby `time_t`) is 32-bit, we *want* to be able to encode timestamps in Git that are currently absurdly far in the future, *even if* the system library is not able to format those timestamps into date strings. So let's just switch to the maximal integer type available, which should be at least 64-bit for all practical purposes these days. It certainly cannot be worse than `unsigned long`, so... Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'builtin/am.c')
0 files changed, 0 insertions, 0 deletions