Matthew E. Luallen reported three bugs on Apple Git 2.50.1 and upstream Git 2.56.0. First, a 1972-dated commit exported with git archive --format=zip gets a legacy DOS date read as 2100, while the extended Unix timestamp keeps 1972. Second, a commit at epoch 4294967296 (2106-02-07) wraps ZIP's four-byte extended timestamp to zero, whereas TAR preserves the value. Third, git fast-import --date-format=raw accepts -32184000 +0000, but git fsck --strict then reports badDate.
René Scharfe explained that git archive writes an Extended Timestamp Extra Field (ID 0x5455, "UT") for each zip entry, as Info-ZIP does, and that its time values are signed 32-bit integers. His patch stops emitting the field when the commit time does not fit. It prepares the field in a strbuf up front and leaves it empty when the value is out of range, which also avoids repeating the condition at the output.
On the wider question of 64-bit times, Scharfe said removing time_t from archive-zip.c would require supplying a 64-bit localtime_r(3) on 32-bit platforms, which he called excessive. It would be easier if archives used a fixed time zone such as UTC rather than the archiver's, but that would change output and break caching schemes. He said the work is too much just to enable two tests, so the tests will get an added requirement for now.
The excerpts do not show how the DOS date issue or the fast-import validation report are being handled.