3 ms·
I noticed that right away, too - I didn't know you could force backdates of git history like that.
by commandlinefan 1y ago
I noticed that right away, too - I didn't know you could force backdates of git history like that.
- BowBun 1y agoAll git data can be modified
- mananaysiempre 1y agoThe GIT_AUTHOR_DATE and GIT_COMMITTER_DATE environment variables[1] are what you use for things like that. (The former can also be overridden by the --date= option to git commit, and there’s also various situational stuff like --reset-author for git commit or --reset-author-date and --committer-date-is-author-date for git rebase. No, that last one is not parody.) [1] https://git-scm.com/docs/git-commit#_commit_information https://git-scm.com/docs/git-commit#_commit_information
- Tor3 1y agoI have source I wrote using SCCS as version control, which later was moved to CVS, preserving the commits as well as commit dates, and at some point moved to Git, again preserving commits and dates. So some of my personal Git repositories have commit entries going back to the late eighties. For any ordinary commit you can simply include "--date=" with the 'git commit' command, e.g. -m "This is an old change" --date="2001-03-02 18:05:47"
- pavon 1y agoI have definitely not done this to fake TDD-ordered commits. Nope not me.
- int_19h 1y agoYou might find this repo interesting: https://github.com/dspinellis/unix-history-repo https://github.com/dspinellis/unix-history-repo