git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "psantosl@codicesoftware.com" <psantosl@codicesoftware.com>
To: Michael Haggerty <mhagger@alum.mit.edu>
Cc: git@vger.kernel.org, "David Suárez" <dsuarezv@codicesoftware.com>
Subject: Re: [ANNOUNCE] GitJungle is out!
Date: Tue, 14 Dec 2010 17:42:28 +0100	[thread overview]
Message-ID: <4D079E74.10408@codicesoftware.com> (raw)
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
> 

      reply	other threads:[~2010-12-14 16:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-13 11:12 [ANNOUNCE] GitJungle is out! psantosl
2010-12-13 13:12 ` Jakub Narebski
2010-12-14 15:46 ` Michael Haggerty
2010-12-14 16:42   ` psantosl [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D079E74.10408@codicesoftware.com \
    --to=psantosl@codicesoftware.com \
    --cc=dsuarezv@codicesoftware.com \
    --cc=git@vger.kernel.org \
    --cc=mhagger@alum.mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).