{"thread":{"id":"38206","subject":"git log --graph --oneline issues (very small edge case)","startedAt":"2014-12-19T16:27:46Z","lastAt":"2014-12-20T00:53:07Z","messageCount":2,"participants":["Jason Pyeron","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"253857","messageId":"71B93170AE5D4ED08EF12CED427299C4@black","threadId":"38206","inReplyTo":null,"subject":"git log --graph --oneline issues (very small edge case)","fromName":"Jason Pyeron","fromEmail":"jpyeron@pdinc.us","sentAt":"2014-12-19T16:27:46Z","receivedAt":"2014-12-19T16:27:46Z","isPatch":false,"sender":{"key":"jpyeron@pdinc.us","avatar":"https://gravatar.com/avatar/c2e53452caa53d940768a1ffc9cf76196d851b9b534b7a39cd39852a70a0508f?d=mp&s=160"},"body":"When a repo has multiple initial commits, the oneline graph can get borked.\n\nIt will put a commit * with no parent directly above the next commit * with no children. This gives the false impression that the two commits are a sequence on a branch. E.g:\n\n* xxxxxxx update of A (#0011)\n* xxxxxxx merge of B->A (#0010)\n|\\\n| * xxxxxxx update of B (#0009)\n* | xxxxxxx update of A (#0008)\n* | xxxxxxx update of A (#0007)\n| * xxxxxxx update of B (#0006)\n| * xxxxxxx update of B (#0005)\n| * xxxxxxx inital commit B (#0004)\n| * xxxxxxx update of A' (#0003)\n| * xxxxxxx fork of A (#0002)\n|/\n* xxxxxxx intial commit A (#0001)\n\nIt should put a blank line after a commit without a parent, like so:\n\n* xxxxxxx update of A (#0011)\n* xxxxxxx merge of B->A (#0010)\n|\\\n| * xxxxxxx update of B (#0009)\n* | xxxxxxx update of A (#0008)\n* | xxxxxxx update of A (#0007)\n| * xxxxxxx update of B (#0006)\n| * xxxxxxx update of B (#0005)\n| * xxxxxxx inital commit B (#0004)\n|\n| * xxxxxxx update of A' (#0003)\n| * xxxxxxx fork of A (#0002)\n|/\n* xxxxxxx intial commit A (#0001)\n\nUnless it is the last commit to be output.\n\nI hit this in the wild https://github.com/pdinc-oss/CipherShed.git, but now that the branches are merged the graph looks fine.\n\n-Jason\n\n--\n-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-\n-                                                               -\n- Jason Pyeron                      PD Inc. http://www.pdinc.us -\n- Principal Consultant              10 West 24th Street #100    -\n- +1 (443) 269-1555 x333            Baltimore, Maryland 21218   -\n-                                                               -\n-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-\nThis message is copyright PD Inc, subject to license 20080407P00.\n"},{"id":"253875","messageId":"xmqqa92jcfbg.fsf@gitster.dls.corp.google.com","threadId":"38206","inReplyTo":"71B93170AE5D4ED08EF12CED427299C4@black","subject":"Re: git log --graph --oneline issues (very small edge case)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2014-12-20T00:53:07Z","receivedAt":"2014-12-20T00:53:07Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"\"Jason Pyeron\" <jpyeron@pdinc.us> writes:\n\n> When a repo has multiple initial commits, the oneline graph can get borked.\n>\n> It will put a commit * with no parent directly above the next commit *\n> with no children. This gives the false impression that the two commits\n> are a sequence on a branch.\n\nSounds vaguely familiar.\n\nhttp://thread.gmane.org/gmane.comp.version-control.git/236708/focus=239580\n\nMy preference is what I wrote after three-dash lines as \"It may\nactually make sense ...  If we did so, the output ... may look like\nthis\" there.\n"}]}