{"thread":{"id":"74","subject":"Parseable commit header","startedAt":"2005-04-17T06:22:36Z","lastAt":"2005-04-17T16:49:24Z","messageCount":3,"participants":["Stefan-W. Hahn","Linus Torvalds","David A. Wheeler"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"450","messageId":"20050417062236.GA3261@scotty.home","threadId":"74","inReplyTo":null,"subject":"Parseable commit header","fromName":"Stefan-W. Hahn","fromEmail":"stefan.hahn@s-hahn.de","sentAt":"2005-04-17T06:22:36Z","receivedAt":"2005-04-17T06:22:36Z","isPatch":false,"sender":{"key":"stefan.hahn@s-hahn.de","avatar":null},"body":"Hi,\n\nafter playing a while with git-pasky it is a crap to interpret the date of\ncommit logs. Though it was a good idea to put the date in a parseable format\n(seconds since), but the format of the commit itself is not good parseable.\n\nFor easy converting the commit log header in readable format it should be in\nanother format, perhaps like mail header: \n- Every field should start al column zero wih filedname end up with a colon.\n- Every fieldname starts with an upcase letter.\n- The dates of author and committer should be fields of it own.\n- The commit message itself is seperated by a blank line.\n\n\nExample current log entry:\n\ncommit fe077e9d16819b72c275ea40b254f22b4d236f8b\ntree 98b57b0310e0e2309fe4a6c24a6abea31a4d6c6d\nparent f0adb6cf1bf603537afff5cf26b90e81321db225\nauthor Petr Baudis <pasky@ucw.cz> 1113684324 +0200\ncommitter Petr Baudis <xpasky@machine> 1113684324 +0200\n\ns/me/commit/ in git log output.\n\n\nShould be:\n\nCommit: fe077e9d16819b72c275ea40b254f22b4d236f8b\nTree: 98b57b0310e0e2309fe4a6c24a6abea31a4d6c6d\nParent: f0adb6cf1bf603537afff5cf26b90e81321db225\nAuthor: Petr Baudis <pasky@ucw.cz> \nAuthor-Date: 1113684324 +0200\nCommitter: Petr Baudis <xpasky@machine> \nCommitter-Dater: 1113684324 +0200\n\ns/me/commit/ in git log output.\n\n\nThis date entries are now easy parseable and convertable.\n\n- Stefan\n\n-- \nStefan-W. Hahn                          It is easy to make things.\n/ mailto:stefan.hahn@s-hahn.de /        It is hard to make things simple.\t\t\t\n\n"},{"id":"487","messageId":"Pine.LNX.4.58.0504170856470.7211@ppc970.osdl.org","threadId":"74","inReplyTo":"20050417062236.GA3261@scotty.home","subject":"Re: Parseable commit header","fromName":"Linus Torvalds","fromEmail":"torvalds@osdl.org","sentAt":"2005-04-17T15:57:43Z","receivedAt":"2005-04-17T15:57:43Z","isPatch":false,"sender":{"key":"torvalds@linux-foundation.org","avatar":"https://avatars.githubusercontent.com/u/1024025?v=4"},"body":"\n\nOn Sun, 17 Apr 2005, Stefan-W. Hahn wrote:\n> \n> after playing a while with git-pasky it is a crap to interpret the date of\n> commit logs. Though it was a good idea to put the date in a parseable format\n> (seconds since), but the format of the commit itself is not good parseable.\n\nActually, it is. The commit stuff removes all special characters from the \nstrings, so '<' and '>' around the email do indeed act as delimiters, and \ncannot exist anywhere else.\n\n\t\t\tLinus\n"},{"id":"500","messageId":"42629394.1090804@dwheeler.com","threadId":"74","inReplyTo":"20050417062236.GA3261@scotty.home","subject":"Re: Parseable commit header","fromName":"David A. Wheeler","fromEmail":"dwheeler@dwheeler.com","sentAt":"2005-04-17T16:49:24Z","receivedAt":"2005-04-17T16:49:24Z","isPatch":false,"sender":{"key":"dwheeler@dwheeler.com","avatar":"https://avatars.githubusercontent.com/u/813150?v=4"},"body":"Stefan-W. Hahn wrote:\n> Hi,\n> \n> after playing a while with git-pasky it is a crap to interpret the date of\n> commit logs. Though it was a good idea to put the date in a parseable format\n> (seconds since), but the format of the commit itself is not good parseable.\n\n> Should be:\n...\n> Committer-Dater: 1113684324 +0200\n\nI'm probably coming in late to the game, but exactly\nwhy is seconds-since-epoch format used instead of a format\nmore easily understood by humans?  Yes, I know tools\ncan easily convert that, but you're already using an ASCII format;\nwhy not just record it in a format that's easily eyeballed like ISO's\nyyyymmddThhmmss [timezone]? E.G.:\n  20050417T171520 +0200\nor some such?  I'm SURE that people will mention things\nlike \"the patch I posted on April 17, 2005\", and having the\npatch format record times that way, directly, would be convenient\nto the poor slobs^H^H^H^H^H developers who come later.\nYes, a tool can handle the conversion, but choosing formats\nso a tool is unneeded for simple stuff is often better....!\n\n--- David A. Wheeler\n"}]}