Skip to contentSkip to conversation

GitJungle is out!

ANNOUNCE [email protected] 3 participants 4 messages Jun 15, 2016

lore
Share & tools
lore
#0 lore raw

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

#1 lore raw
Quoted 8 lines · "[email protected]" <[email protected]> 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...

Quoted 8 lines

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

Signature · 3 lines
Jakub Narebski
Poland
ShadeHawk on #git
#2 lore raw
In reply to [email protected]
Quoted 5 lines · On 12/13/2010 12:12 PM, [email protected] 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

Signature · 3 lines
Michael Haggerty
[email protected]
http://softwareswirl.blogspot.com/
#3 lore raw

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

Quoted 22 lines · Michael Haggerty
Quoted 5 lines · On 12/13/2010 12:12 PM, [email protected] 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