{"thread":{"id":"17769","subject":"git log --graph and root commits","startedAt":"2009-02-13T04:16:30Z","lastAt":"2009-02-14T00:40:58Z","messageCount":5,"participants":["Sitaram Chamarty","Johannes Schindelin","Jakub Narebski"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"104472","messageId":"slrngp9t0u.va9.sitaramc@sitaramc.homelinux.net","threadId":"17769","inReplyTo":null,"subject":"git log --graph and root commits","fromName":"Sitaram Chamarty","fromEmail":"sitaramc@gmail.com","sentAt":"2009-02-13T04:16:30Z","receivedAt":"2009-02-13T04:16:30Z","isPatch":false,"sender":{"key":"sitaramc@gmail.com","avatar":"https://avatars.githubusercontent.com/u/43316?v=4"},"body":"I was wondering if there was any way, when using 'git log\n--graph --pretty=oneline' to get a different marker (perhaps\nan underscore) for a root commit.\n\nI have a couple of repos in which there are multiple roots\n(a bit like the git tree itself, which has separately rooted\nhtml and man branches), and it would be nice to see some\nsign of that break in the git log graph.\n\nThanks,\n\nSitaram\n"},{"id":"104510","messageId":"alpine.DEB.1.00.0902131237490.10279@pacific.mpi-cbg.de","threadId":"17769","inReplyTo":"slrngp9t0u.va9.sitaramc@sitaramc.homelinux.net","subject":"Re: git log --graph and root commits","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2009-02-13T11:41:08Z","receivedAt":"2009-02-13T11:41:08Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Fri, 13 Feb 2009, Sitaram Chamarty wrote:\n\n> I was wondering if there was any way, when using 'git log\n> --graph --pretty=oneline' to get a different marker (perhaps\n> an underscore) for a root commit.\n\nIs it not enough that the line ends? That is a pretty obvious visual \nmarker for me that this is a root commit. But I see that you are _asking_ \nfor the lines not to be shown, by using --pretty=oneline.\n\nYou might be interested in this instead:\n\n\tgit log --graph --pretty=format:'%h %s%n'\n\nHth,\nDscho\n"},{"id":"104520","messageId":"slrngpb2gl.rhg.sitaramc@sitaramc.homelinux.net","threadId":"17769","inReplyTo":"alpine.DEB.1.00.0902131237490.10279@pacific.mpi-cbg.de","subject":"Re: git log --graph and root commits","fromName":"Sitaram Chamarty","fromEmail":"sitaramc@gmail.com","sentAt":"2009-02-13T14:56:21Z","receivedAt":"2009-02-13T14:56:21Z","isPatch":false,"sender":{"key":"sitaramc@gmail.com","avatar":"https://avatars.githubusercontent.com/u/43316?v=4"},"body":"On 2009-02-13, Johannes Schindelin wrote:\n> On Fri, 13 Feb 2009, Sitaram Chamarty wrote:\n\n>> I was wondering if there was any way, when using 'git log\n>> --graph --pretty=oneline' to get a different marker (perhaps\n>> an underscore) for a root commit.\n\n> Is it not enough that the line ends? That is a pretty obvious visual \n> marker for me that this is a root commit. But I see that you are _asking_ \n> for the lines not to be shown, by using --pretty=oneline.\n\nYes; I'm short on vertical space here.\n\n> You might be interested in this instead:\n>\n> \tgit log --graph --pretty=format:'%h %s%n'\n\nIt doubles the height requirement, but you gave me an idea:\n\n git log --graph --pretty=tformat:'%h <%p> %s' --all |\n perl -pe '$_.=\"----\\n\" if /<>/; s/<.*?> //'\n\nThanks for pointing me in the right direction.\n\nRegards,\n\nSitaram\n"},{"id":"104526","messageId":"m3wsbuthp1.fsf@localhost.localdomain","threadId":"17769","inReplyTo":"slrngpb2gl.rhg.sitaramc@sitaramc.homelinux.net","subject":"Re: git log --graph and root commits","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2009-02-13T16:39:08Z","receivedAt":"2009-02-13T16:39:08Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"Sitaram Chamarty writes:\n> On 2009-02-13, Johannes Schindelin wrote:\n>> On Fri, 13 Feb 2009, Sitaram Chamarty wrote:\n> \n>>> I was wondering if there was any way, when using 'git log\n>>> --graph --pretty=oneline' to get a different marker (perhaps\n>>> an underscore) for a root commit.\n>>\n>> You might be interested in this instead:\n>>\n>> \tgit log --graph --pretty=format:'%h %s%n'\n> \n> It doubles the height requirement, but you gave me an idea:\n> \n> git log --graph --pretty=tformat:'%h <%p> %s' --all |\n> perl -pe '$_.=\"----\\n\" if /<>/; s/<.*?> //'\n> \n> Thanks for pointing me in the right direction.\n\nGaaah... I tried running it on git.git :-))))\n\n-- \nJakub Narebski\nPoland\nShadeHawk on #git\n"},{"id":"104560","messageId":"slrngpc4op.jdo.sitaramc@sitaramc.homelinux.net","threadId":"17769","inReplyTo":"m3wsbuthp1.fsf@localhost.localdomain","subject":"Re: git log --graph and root commits","fromName":"Sitaram Chamarty","fromEmail":"sitaramc@gmail.com","sentAt":"2009-02-14T00:40:58Z","receivedAt":"2009-02-14T00:40:58Z","isPatch":false,"sender":{"key":"sitaramc@gmail.com","avatar":"https://avatars.githubusercontent.com/u/43316?v=4"},"body":"On 2009-02-13, Jakub Narebski wrote:\n> Sitaram Chamarty writes:\n>> On 2009-02-13, Johannes Schindelin wrote:\n\n>>> \tgit log --graph --pretty=format:'%h %s%n'\n\n>> It doubles the height requirement, but you gave me an idea:\n>> \n>> git log --graph --pretty=tformat:'%h <%p> %s' --all |\n>> perl -pe '$_.=\"----\\n\" if /<>/; s/<.*?> //'\n>> \n>> Thanks for pointing me in the right direction.\n>\n> Gaaah... I tried running it on git.git :-))))\n\n:-)\n\nSeriously, I find 'log --graph' is useful on projects where\nnot everyone is an expert and things might go a little\nhaywire here and there. People merge the wrong thing with\nthe wrong other thing, maybe, and you want to see how\nprecisely they got there.\n\nA project managed by git.gods can become a lot more complex\nand not have to actually care about this visualisation.\n\nOf course, gitk is really good and manages a lot more\ncomplexity, obviously, but I like 'log --graph' also. And\nI've sort of fallen in love with --simplify-by-decoration\ntoo. Very cool stuff.\n\nThe things you can do on an xterm...!\n"}]}