git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: Bill Lear <rael@zopyra.com>
Cc: "Santi Béjar" <santi@agolina.net>,
	rhlee <richard@webdezign.co.uk>,
	git@vger.kernel.org
Subject: Re: Git graph with branch labels for all paths in text environment
Date: Mon, 16 Nov 2009 16:27:46 +0100	[thread overview]
Message-ID: <4B016F72.7000001@drmicha.warpmail.net> (raw)
In-Reply-To: <19201.21478.127959.431877@lisa.zopyra.com>

Bill Lear venit, vidit, dixit 16.11.2009 14:30:
> On Monday, November 16, 2009 at 13:23:10 (+0100) Santi Béjar writes:
>> On Mon, Nov 16, 2009 at 1:03 PM, rhlee <richard@webdezign.co.uk> wrote:
>>> Is there anyway to to view a text based git grah that shows all paths with
>>> the branch labels? Like a on gitk but ncurses based?
>>
>> For third-party tools you can check:
>>
>> http://git-scm.com/tools
> 
> Anything that can print this?:
> 
>                                        H---I---J topicB
>                                       /
>                              E---F---G  topicA
>                             /
>                A---B---C---D  master
> 
> I've always liked the text-based format that keeps things in-line, as
> above.  Very readable.  I thought someone on this list posted
> something about a tool that could produce such graphs from
> reasonably-sized git repos.  Anyone have such a thing?

You really mean horizontally? I know those wide screen monitors are
becoming ubiquitious, but still...

Or are you more after the "in-line" part in the sense that "each branch
is on its line"? This is a bit difficult to define, though (the graph
above is linear, e.g.).

Michael

  reply	other threads:[~2009-11-16 15:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-16 12:03 Git graph with branch labels for all paths in text environment rhlee
2009-11-16 12:23 ` Santi Béjar
2009-11-16 13:30   ` Bill Lear
2009-11-16 15:27     ` Michael J Gruber [this message]
2009-11-21 17:50 ` Jonas Fonseca
2009-11-23  9:56   ` rhlee

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=4B016F72.7000001@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=rael@zopyra.com \
    --cc=richard@webdezign.co.uk \
    --cc=santi@agolina.net \
    /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).