From: rhlee <richard@webdezign.co.uk>
To: git@vger.kernel.org
Subject: Re: Git graph with branch labels for all paths in text environment
Date: Mon, 23 Nov 2009 01:56:27 -0800 (PST) [thread overview]
Message-ID: <1258970187042-4050140.post@n2.nabble.com> (raw)
In-Reply-To: <2c6b72b30911210950m7f90f210saf3c32c1a3cbdebe@mail.gmail.com>
Jonas Fonseca wrote:
>
> You can browse all branches by using: tig --all
>
Thanks this great as this saves me from quitting tig to view all branch
histories.
Jonas Fonseca wrote:
>
> However, the graph drawing is rather poor for complex git histories.
>
I'm working on 3-4 current branches and it's fine for me.
Thanks,
Richard
--
View this message in context: http://n2.nabble.com/Git-graph-with-branch-labels-for-all-paths-in-text-environment-tp4011651p4050140.html
Sent from the git mailing list archive at Nabble.com.
prev parent reply other threads:[~2009-11-23 9:56 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
2009-11-21 17:50 ` Jonas Fonseca
2009-11-23 9:56 ` rhlee [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=1258970187042-4050140.post@n2.nabble.com \
--to=richard@webdezign.co.uk \
--cc=git@vger.kernel.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).