4 ms·
I didn't downvote you, but what you say doesn't make much sense. git is distributed and works offline, this means that nothing could prevent you from making co
by codesnik 8y ago
I didn't downvote you, but what you say doesn't make much sense.
git is distributed and works offline, this means that nothing could prevent you from making commit with a "fake" date, you always can change time on your machine. So there's nothing really hackish in that, and that has nothing to do with format in which time stored in git internally. And you can have legitimate uses for "faking" commit date. I'd say repository above is an example of such a legitimate use.
- tinus_hn 8y agoThe format Git uses determines the range of dates it can store. If it uses the normal Unix epoch system 0 means 1-1-1970 so you can’t represent dates before that.
- theclaw 8y agoI thought unix time was a signed integer, so you can go negative all the way back to 1901: $ perl -e 'print gmtime(-2147483648).""' Fri Dec 13 20:45:52 1901
- rusk 8y agoIt’s more a formality I think. Since recording of atomic time started in the early 1970s it’s accepted that an atomic second is an actual second back as far as 1970. No assertion of accuracy is made beyond that. Of course otherwise you can negative offset as much as you like beyond that but because of physics and stuff it can’t be treated with the same level of certainty or something.