git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Baudis <pasky@suse.cz>
To: Tom Werner <pubsub@rubyisawesome.com>
Cc: git@vger.kernel.org
Subject: Re: Git graph on GitHub
Date: Wed, 15 Oct 2008 14:20:22 +0200	[thread overview]
Message-ID: <20081015122022.GW10544@machine.or.cz> (raw)
In-Reply-To: <530345950810150047v75bfbf9clebbb8a406b172c4c@mail.gmail.com>

  Hi,

On Wed, Oct 15, 2008 at 12:47:52AM -0700, Tom Werner wrote:
> We've just pushed out an update to the Network Graph on GitHub this
> evening that finally allows us to draw very large repositories
> (including Git). We're mirroring the Git repo on the site and I
> thought it might be interesting for people to see this visualization.
> Enjoy!
> 
> http://github.com/git/git/network
> 
> Let me know if you have any ideas for improvements on the graph. I'm
> always looking for ways to enhance it.

  it's generally nice, but I think it could be much more useful yet. :-)

  Generally, I find its information density very low. I see only tiny
dots connected by lines at the top of the screen (rest grey) and if I
want to know _what_ commits are actually there, I need to carefully
hover over the scattered tiny dots. So my question is, exactly what kind
of information do you seek to present primarily? Based on what I see,
the answer seems to be just "how hairy the project history is", and I'm
wondering if maybe some other class of information would be more
interesting. IOW, what about using that blank grey area to show the
commit subjects? ;-)

  Right now, your repository contains only the 'master' branch. I guess
you want to setup a --mirror repository instead of pulling?

  Also, it would be pretty nifty if you could tag lines of past topic
branches based on the merge commit message. E.g. mark the blue line
short in the past as pb/gitweb-tagcloud based on the 3e3d4ee merge. On
the other hand, I'm not sure how well would it work visually if the
topic branches are very short and merged right away.

-- 
				Petr "Pasky" Baudis
People who take cold baths never have rheumatism, but they have
cold baths.

  parent reply	other threads:[~2008-10-15 12:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-15  7:47 Git graph on GitHub Tom Werner
2008-10-15  8:24 ` Michael J Gruber
2008-10-15 12:20 ` Petr Baudis [this message]
2008-10-18 20:56 ` Jakub Narebski
2008-10-20 15:21   ` Pedro Melo

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=20081015122022.GW10544@machine.or.cz \
    --to=pasky@suse.cz \
    --cc=git@vger.kernel.org \
    --cc=pubsub@rubyisawesome.com \
    /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).