# [ANNOUNCE] GitJungle is out! 4 messages from 2010-12-13 to 2010-12-14. Participants: psantosl@codicesoftware.com, Jakub Narebski, Michael Haggerty. Thread: https://gitlist.dev/t/26038 ## psantosl@codicesoftware.com, 2010-12-13 11:12 Subject: [ANNOUNCE] GitJungle is out! Message-ID: <4D05FF8D.7080306@codicesoftware.com> URL: https://gitlist.dev/e/4D05FF8D.7080306%40codicesoftware.com ``` Hi all, We've just released GitJungle (http://www.plasticscm.com/labs/gitjungle.aspx), a git branch explorer based on the same codebase we use in our version control product, plastic scm. We wanted to call it something like GitForest (you know, so many branches and trees :P) but the name was already reserved... GitJungle is a beta and works on Linux, Mac and Windows and basically we'd love to get feedback. The drawing approach we use is a little bit different from what other git tools are using: we draw horizontally instead of vertically, we think it is a better way but, you know, it is probably a matter of preference. I'd really like if you could give it a try and of course any feedback (including tough critics) will be more than welcome. Thanks, pablo ``` ## Jakub Narebski, 2010-12-13 13:12 Subject: Re: [ANNOUNCE] GitJungle is out! Message-ID: URL: https://gitlist.dev/e/m3d3p54y21.fsf%40localhost.localdomain In-Reply-To: <4D05FF8D.7080306@codicesoftware.com> ``` "psantosl@codicesoftware.com" writes: > We've just released GitJungle > (http://www.plasticscm.com/labs/gitjungle.aspx), a git branch explorer > based on the same codebase we use in our version control product, > plastic scm. > > We wanted to call it something like GitForest (you know, so many > branches and trees :P) but the name was already reserved... > > GitJungle is a beta and works on Linux, Mac and Windows and basically > we'd love to get feedback. The drawing approach we use is a little bit > different from what other git tools are using: we draw horizontally > instead of vertically, we think it is a better way but, you know, it is > probably a matter of preference. > > I'd really like if you could give it a try and of course any feedback > (including tough critics) will be more than welcome. Could you add information about GitJungle in the correct place at https://git.wiki.kernel.org/index.php/InterfacesFrontendsAndTools page on Git Wiki? Thanks in advance -- Jakub Narebski Poland ShadeHawk on #git ``` ## Michael Haggerty, 2010-12-14 15:46 Subject: Re: [ANNOUNCE] GitJungle is out! Message-ID: <4D079155.4020102@alum.mit.edu> URL: https://gitlist.dev/e/4D079155.4020102%40alum.mit.edu In-Reply-To: <4D05FF8D.7080306@codicesoftware.com> ``` On 12/13/2010 12:12 PM, psantosl@codicesoftware.com wrote: > We've just released GitJungle > [...] The drawing approach we use is a little bit > different from what other git tools are using: we draw horizontally > instead of vertically, we think it is a better way but, you know, it is > probably a matter of preference. Given that git doesn't permanently record the branch that a commit was first made on, how do you decide on what row to draw a commit? E.g., if I have two branches A and B that share a common ancestor o-o <- A / o-o-o \ o-o <- B how do you decide whether to draw the ancestor on the row for A vs. the row for B? Michael -- Michael Haggerty mhagger@alum.mit.edu http://softwareswirl.blogspot.com/ ``` ## psantosl@codicesoftware.com, 2010-12-14 16:42 Subject: Re: [ANNOUNCE] GitJungle is out! Message-ID: <4D079E74.10408@codicesoftware.com> URL: https://gitlist.dev/e/4D079E74.10408%40codicesoftware.com In-Reply-To: <4D079155.4020102@alum.mit.edu> ``` Hi Michael, The commits are walked from the heads, starting on master. Once a commit is assigned to a branch, it stays there. So the diagram would have a different aspect if the heads were walked in a different order. David (in CC) is the one to ask for details, he's still struggling to get a better render than what we have right now. Thanks, pablo On 12/14/2010 16:46, Michael Haggerty wrote: > On 12/13/2010 12:12 PM, psantosl@codicesoftware.com wrote: >> We've just released GitJungle >> [...] The drawing approach we use is a little bit >> different from what other git tools are using: we draw horizontally >> instead of vertically, we think it is a better way but, you know, it is >> probably a matter of preference. > > Given that git doesn't permanently record the branch that a commit was > first made on, how do you decide on what row to draw a commit? E.g., if > I have two branches A and B that share a common ancestor > > o-o <- A > / > o-o-o > \ > o-o <- B > > how do you decide whether to draw the ancestor on the row for A vs. the > row for B? > > Michael > ```