Re:Indie game Haunts unable to compile its Go code
by bluehex on Wednesday May 15, 2013 @04:30AM
(#5710815)
Unless he lost his local copy he wouldn't even need to guess what commit around the date he was at in each repo.
The info is stored in the ref-log of the local git repo, (as well as the dependencies' local repos).
So you could rewind all the repos to where they were at a particular date/time with:
`git co HEAD@{2012-11-26 18:30:00}` in each repo. If you run that same command in the project repo, and the dependency repos you should have a snapshot of the developers local checkout at that time.
HEAD could be a branch name or whatever ref. You can specify the time like ref@{2.days.3.hours.25.minutes.ago} as well, and these time specifiers work wherever you can specify a revision for example `git log -n1 master@{yesterday}`
So you could rewind all the repos to where they were at a particular date/time with: `git co HEAD@{2012-11-26 18:30:00}` in each repo. If you run that same command in the project repo, and the dependency repos you should have a snapshot of the developers local checkout at that time.
HEAD could be a branch name or whatever ref. You can specify the time like ref@{2.days.3.hours.25.minutes.ago} as well, and these time specifiers work wherever you can specify a revision for example `git log -n1 master@{yesterday}`
see: https://www.kernel.org/pub/software/scm/git/docs/gitrevision...