{"thread":{"id":"27872","subject":"git log decipher","startedAt":"2011-07-21T01:39:11Z","lastAt":"2011-07-21T11:41:50Z","messageCount":3,"participants":["gbhumphrey","Shawn Pearce","Jakub Narebski"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"171770","messageId":"1311212351172-6605124.post@n2.nabble.com","threadId":"27872","inReplyTo":null,"subject":"git log decipher","fromName":"gbhumphrey","fromEmail":"greg_spam@gbhumphrey.com","sentAt":"2011-07-21T01:39:11Z","receivedAt":"2011-07-21T01:39:11Z","isPatch":false,"sender":{"key":"greg_spam@gbhumphrey.com","avatar":null},"body":"Hi so in the .git/logs/refs/heads there are log files, i'm tryign to decipher\nthe timestamp, at least I think it's a time stamp. An entry looks like this:\na391d7a96af8c06a626eec23565ceccef81bc350\nfdfb6d8c87521d56d8a6034e8575304013ecdd6c Greg Humphrey <XXX@XXXX.com>\n1307594233 -0700\tmerge US199: Merge made by recursive.\n\nThe \"1307594233 -0700\" seems to be a timestamp, but I'm not sure what\nformat, anyone have any ideas how to convert to a human readable?\n\n\n\n--\nView this message in context: http://git.661346.n2.nabble.com/git-log-decipher-tp6605124p6605124.html\nSent from the git mailing list archive at Nabble.com.\n"},{"id":"171771","messageId":"CAJo=hJvvsqki3tLoQRjgf7vQpcH6EHMXXxUbYALw8MvtLzF=gA@mail.gmail.com","threadId":"27872","inReplyTo":"1311212351172-6605124.post@n2.nabble.com","subject":"Re: git log decipher","fromName":"Shawn Pearce","fromEmail":"spearce@spearce.org","sentAt":"2011-07-21T01:50:45Z","receivedAt":"2011-07-21T01:50:45Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"On Wed, Jul 20, 2011 at 18:39, gbhumphrey wrote:\n> Hi so in the .git/logs/refs/heads there are log files, i'm tryign to decipher\n> the timestamp, at least I think it's a time stamp. An entry looks like this:\n> a391d7a96af8c06a626eec23565ceccef81bc350\n> fdfb6d8c87521d56d8a6034e8575304013ecdd6c Greg Humphrey <XXX@XXXX.com>\n> 1307594233 -0700        merge US199: Merge made by recursive.\n>\n> The \"1307594233 -0700\" seems to be a timestamp, but I'm not sure what\n> format, anyone have any ideas how to convert to a human readable?\n\nThe first number is the seconds since the UNIX epoch. A standard\ntime_t... in base 10. :-)\n\nThe second number is the timezone offset from GMT, in HHMM format. So\n-0700 is 7 hours behind GMT.\n\nIts the same format as what appears in a Git commit object for either\nthe author or committer line.\n\n-- \nShawn.\n"},{"id":"171777","messageId":"m3wrfbsvxv.fsf@localhost.localdomain","threadId":"27872","inReplyTo":"1311212351172-6605124.post@n2.nabble.com","subject":"Re: git log decipher","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2011-07-21T11:41:50Z","receivedAt":"2011-07-21T11:41:50Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"gbhumphrey writes:\n\n> Hi so in the .git/logs/refs/heads there are log files, i'm tryign to decipher\n> the timestamp, at least I think it's a time stamp. An entry looks like this:\n> a391d7a96af8c06a626eec23565ceccef81bc350\n> fdfb6d8c87521d56d8a6034e8575304013ecdd6c Greg Humphrey <XXX@XXXX.com>\n> 1307594233 -0700\tmerge US199: Merge made by recursive.\n> \n> The \"1307594233 -0700\" seems to be a timestamp, but I'm not sure what\n> format, anyone have any ideas how to convert to a human readable?\n\nIf you want to *view* this information, why not use \"git reflog\" or\n\"git log -g\" instead of reading raw files?\n\nIf you want to *parse* this information:\n - \"1307594233\" is Unix epoch, i.e. number of seconds since\n '00:00:00 1970-01-01 UTC'; it is independent on timezone\n - \"-0700\" is RFC-2822 style numeric timezone; informational\n\nFrom RFC-2822 (http://tools.ietf.org/html/rfc2822#section-3.3)\n\n The zone specifies the offset from Coordinated Universal Time (UTC,\n formerly referred to as \"Greenwich Mean Time\") that the date and\n time-of-day represent. The \"+\" or \"-\" indicates whether the\n time-of-day is ahead of (i.e., east of) or behind (i.e., west of)\n Universal Time. The first two digits indicate the number of hours\n difference from Universal Time, and the last two digits indicate the\n number of minutes difference from Universal Time. (Hence, +hhmm\n means +(hh * 60 + mm) minutes, and -hhmm means -(hh * 60 + mm)\n minutes). The form \"+0000\" SHOULD be used to indicate a time zone at\n Universal Time. Though \"-0000\" also indicates Universal Time, it is\n used to indicate that the time was generated on a system that may be\n in a local time zone other than Universal Time and therefore\n indicates that the date-time contains no information about the local\n time zone.\n\n-- \nJakub Narębski\n"}]}