From: "Björn Steinbrink" <B.Steinbrink@gmx.de>
To: Joshua Haberman <joshua@reverberate.org>
Cc: git@vger.kernel.org
Subject: Re: visualizing Git's Git repo
Date: Tue, 27 May 2008 02:41:32 +0200 [thread overview]
Message-ID: <20080527004132.GA6400@atjola.homenet> (raw)
In-Reply-To: <CA563F5A-5E12-42F7-BDFD-04FE3A882028@reverberate.org>
On 2008.05.26 13:47:33 -0700, Joshua Haberman wrote:
> I'm a casual Git user. One thing that's been troubling me about Git is
> that when I look at Git's own Git repository, the revision history is not
> at all easy to understand. I like to view my own Git repositories with:
>
> $ gitk --all --date-order
>
> When I run this command, what I'm really asking is "give me a visual
> summary of what's up with my project lately." But with Git's
> repository, there are far too many branches and merges for this view to
> make any kind of visual sense.
>
> So my questions are:
>
> 1. what do you all do to get a high-level view of what's going on with
> Git development? do you use gitk? if so, what options?
Doesn't make much sense with --all, but if you only view one branch, eg.
origin/master or origin/next, --no-merges might produce an output that's
more suitable for you.
Björn
next prev parent reply other threads:[~2008-05-27 0:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-26 20:47 visualizing Git's Git repo Joshua Haberman
2008-05-26 22:59 ` Eric Hanchrow
2008-05-26 23:42 ` Joshua Haberman
2008-05-26 23:46 ` Shawn O. Pearce
2008-05-27 0:41 ` Björn Steinbrink [this message]
2008-05-27 20:36 ` Joshua Haberman
2008-05-27 23:49 ` Jeff King
2008-05-28 3:15 ` Linus Torvalds
2008-05-28 8:39 ` Jakub Narebski
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=20080527004132.GA6400@atjola.homenet \
--to=b.steinbrink@gmx.de \
--cc=git@vger.kernel.org \
--cc=joshua@reverberate.org \
/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).