{"thread":{"id":"13432","subject":"How to capture date/time of push vs. local commit?","startedAt":"2008-05-08T13:48:19Z","lastAt":"2008-05-08T14:06:48Z","messageCount":3,"participants":["Doug Reiland","Matthias Kestenholz","Eric Hanchrow"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"76371","messageId":"6844644e0805080648g72c4b767l4bcf48ade319bf77@mail.gmail.com","threadId":"13432","inReplyTo":null,"subject":"How to capture date/time of push vs. local commit?","fromName":"Doug Reiland","fromEmail":"dreiland@gmail.com","sentAt":"2008-05-08T13:48:19Z","receivedAt":"2008-05-08T13:48:19Z","isPatch":false,"sender":{"key":"dreiland@gmail.com","avatar":null},"body":"I have a main repository that folks clone and push to. Using git-log\nfor example on the main repository can show some confusing (too me at\nleast) date.\n\nFor example, I clone. I make changes to my repository and commit on\nMonday. I don't push my changes to the main repository until\nWednesday.\n\ngit-log on main repository show changes made on Monday.\nThis makes it hard to determine when folks really got stuff into the\nmain repository.\n\nIs there way to change this so (in my example), I can determine those\nchanges weren't in place until Wednesday? Something in configuration\nfile or perhaps just a different option to git-log.\n\nThanks in advance.\n"},{"id":"76373","messageId":"87hcd85258.fsf@offby1.atm01.sea.blarg.net","threadId":"13432","inReplyTo":"6844644e0805080648g72c4b767l4bcf48ade319bf77@mail.gmail.com","subject":"Re: How to capture date/time of push vs. local commit?","fromName":"Eric Hanchrow","fromEmail":"offby1@blarg.net","sentAt":"2008-05-08T13:57:55Z","receivedAt":"2008-05-08T13:57:55Z","isPatch":false,"sender":{"key":"eric.hanchrow@gmail.com","avatar":"https://avatars.githubusercontent.com/u/3145?v=4"},"body":"I would think you could get what you want with sufficient grovelling of\nthe files in .../.git/logs/.\n-- \nIt is a truth universally acknowledged, that any language in\npossession of a rich syntax, must be in want of a rewrite.\n        -- Piers Cawley\n"},{"id":"76372","messageId":"1210255608.6737.12.camel@futex","threadId":"13432","inReplyTo":"6844644e0805080648g72c4b767l4bcf48ade319bf77@mail.gmail.com","subject":"Re: How to capture date/time of push vs. local commit?","fromName":"Matthias Kestenholz","fromEmail":"mk@spinlock.ch","sentAt":"2008-05-08T14:06:48Z","receivedAt":"2008-05-08T14:06:48Z","isPatch":false,"sender":{"key":"matthias@spinlock.ch","avatar":"https://gravatar.com/avatar/bc18f396e70163d09ab458a341b1decb7e8b6ee3aa2c0c954ec20162e67c4d46?d=mp&s=160"},"body":"Doug,\n\nOn Thu, 2008-05-08 at 09:48 -0400, Doug Reiland wrote:\n> I have a main repository that folks clone and push to. Using git-log\n> for example on the main repository can show some confusing (too me at\n> least) date.\n> \n> For example, I clone. I make changes to my repository and commit on\n> Monday. I don't push my changes to the main repository until\n> Wednesday.\n> \n> git-log on main repository show changes made on Monday.\n> This makes it hard to determine when folks really got stuff into the\n> main repository.\n> \n> Is there way to change this so (in my example), I can determine those\n> changes weren't in place until Wednesday? Something in configuration\n> file or perhaps just a different option to git-log.\n> \n> Thanks in advance.\n\nThis is the nature of a distributed version control system. The\ntimestamps cannot be used to establish a ordering of commits.\n\nIf you have reflogs enabled on the server (see man git-reflog) the\ninformation there can help you find out when the pushes have been made.\nThere is no mechanism to transfer these reflogs into your local\nrepository, since reflogs are always local to a single repository. If\nyou have access to the server, you can examine the reflogs there. (f.e.\nusing git log -g or git reflog)\n\n-- \nhttp://spinlock.ch/blog/\n"}]}