On Mon, Feb 22, 2016 at 7:04 PM, Mark Miller <[email protected]> wrote:
> Nevermind. It is telling me the time that these changes were committed > anywhere, not when they were pushed to github, right? > Yes, exactly. More than you wanted to know: There are two dates in git commit data, the "author date" and the "committer date" (going along with two different attributions). They are usually the same, but are different if a commit was amended or e.g. mailed by the author as a patch and turned into a git commit by someone else. _Neither_ of these dates is the date of push: commits are not modified by being pushed. So to be able to do what you were first expecting, GitHub would have to be keeping a mapping of commit → push the commit was first seen in → date thereof. And then is “first seen in” for the current branch, or any branch (including deleted ones), or what? Distributed systems are necessarily more complex, film at <error: true ordering of events not definable>. -- --- You received this message because you are subscribed to the Google Groups "Google Caja Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
