4 ms·

It looks like they set the commit dates to match the release dates: https://github.com/Microsoft/MS-DOS/commits/master https://github.com/Microsoft/MS-DOS/commi

It looks like they set the commit dates to match the release dates: https://github.com/Microsoft/MS-DOS/commits/master https://github.com/Microsoft/MS-DOS/commits/master

userbinator 8y ago
Interesting. More explanation: https://hackernoon.com/how-to-hack-github-kind-of-12b08a46d02e?gi=6c1136aeb6d5 https://hackernoon.com/how-to-hack-github-kind-of-12b08a46d0... It looks like git uses the standard Unix epoch for its internal timestamp format, and not e.g. a format unable to represent dates before its creation, but that still means it can't really handle pre-Unix dates: https://stackoverflow.com/questions/21787872/is-it-possible-to-set-a-git-commit-to-have-a-timestamp-prior-to-1970 https://stackoverflow.com/questions/21787872/is-it-possible-... Edit: downvoters, care to explain what I'm wrong about?
- deleted 8y ago
  [deleted]
- philipkglass 8y ago
  The second half of your post appears to imply that MS-DOS source releases would properly be dated "pre-Unix" (pre-1970), but they're not that old. I didn't downvote.
- 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 ago
    The 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 ago
      I 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 ago
        It’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.

It looks like they set the commit dates to match the release dates: https://github.com/Microsoft/MS-DOS/commits/master https://github.com/Microsoft/MS-DOS/commits/master

userbinator 8y ago

Interesting. More explanation: https://hackernoon.com/how-to-hack-github-kind-of-12b08a46d02e?gi=6c1136aeb6d5 https://hackernoon.com/how-to-hack-github-kind-of-12b08a46d0... It looks like git uses the standard Unix epoch for its internal timestamp format, and not e.g. a format unable to represent dates before its creation, but that still means it can't really handle pre-Unix dates: https://stackoverflow.com/questions/21787872/is-it-possible-to-set-a-git-commit-to-have-a-timestamp-prior-to-1970 https://stackoverflow.com/questions/21787872/is-it-possible-... Edit: downvoters, care to explain what I'm wrong about?

deleted 8y ago
[deleted]
philipkglass 8y ago
The second half of your post appears to imply that MS-DOS source releases would properly be dated "pre-Unix" (pre-1970), but they're not that old. I didn't downvote.
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 ago
  The 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 ago
    I 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 ago
      It’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.