Reputation: 1039
I was browsing http://arago-project.org/git/projects/linux-omap3.git repo and came across a strange date-thing, which basically says that parent commit is a year younger than its child.
How is this possible?
user@ubuntu1004:/f/linux-omap3$ git log -2 --parents 4b8db3b
commit 4b8db3b368f5601717e3ffee0051628ba33172d3 3c0eee3fe6a3a1c745379547c7e7c904aa64f6d5
Author: Kevin Hilman <[email protected]>
Date: Fri Aug 20 11:19:52 2010 -0700
OMAP: bus-level PM: enable use of runtime PM API for suspend/resume
[...skipped...]
Cc: Rajendra Nayak <[email protected]>
Signed-off-by: Kevin Hilman <[email protected]>
commit 3c0eee3fe6a3a1c745379547c7e7c904aa64f6d5 65f42886e24be2197b1263f138eabf40c6774d00
Author: Linus Torvalds <[email protected]>
Date: Tue Jan 4 16:50:19 2011 -0800
Linux 2.6.37
Upvotes: 5
Views: 494
Reputation: 20419
The accepted answer is way more technically insightful, but I'll just add how this actually happened to me. I was debugging an issue that was affected by the local computer date, and was actively changing my system clock to track down the bug. After fixing it I committed everything to git unaware that my system clock was still set 2 months in the future, thereby screwing up my git history since I only noticed a few days later when commits showed up out of order in Github (d'oh!). This is supposedly fixable, though I haven't tried it yet.
Upvotes: 2
Reputation: 1324033
As mentioned in the comments:
GIT_AUTHOR_DATE
and GIT_COMMITER_DATE
: See working with date in Git.What you see could be the result of a:
git rebase
does actually not change authors' timestamps by default: see "git rebase without changing commit timestamps".GIT_AUTHOR_DATE
Upvotes: 5