3 ms·

go has a commit from 1972: http://bit.ly/1sYa7qR http://bit.ly/1sYa7qR We recently had a look at first commits [1]. Most large projects start out as a code dum

by teh 12y ago

go has a commit from 1972: http://bit.ly/1sYa7qR http://bit.ly/1sYa7qR We recently had a look at first commits [1]. Most large projects start out as a code dump, so are less interesting. [1] https://blog.wearewizards.io/first-commits https://blog.wearewizards.io/first-commits

dribnet 12y ago
It's my understanding that - because of obscure constants in the git codebase - it's a bad idea to use dates before Sat, 03 Mar 1973 09:46:40 GMT because the usable git epoch is 1970 + 100000000s. More details available here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625480 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625480 FWIW: I routinely start my git repos with an empty commit to allow history rewrites and use Jan 1st, 1974 as my own epoch.
- spb 12y ago
  Pretty sure that bug has since been fixed, I generated a dummy commit with a date of 0 a few months ago.
- codyps 12y ago
  FYI: git supports rewrites to the implicit root commit with `git rebase --root` (and similar), there isn't a need for an extra empty commit.
_almosnow 12y ago
How come the first commit for go is from that year? Didn't go appeared around 2007-2008 ?
- lstamour 12y ago
  The file is not written in Go. It appears to be a "hello world". Since all these commits predate their git storage technology, it's a form of back-dating...
- teh 12y ago
  It's a homage to b, one of go's ancestors.