From: "Ping Yin" <pkufranky@gmail.com>
To: "Jan Engelhardt" <jengelh@computergmbh.de>
Cc: git@vger.kernel.org
Subject: Re: [announce] text-based tree visualizer
Date: Mon, 17 Mar 2008 21:40:43 +0800 [thread overview]
Message-ID: <46dff0320803170640g52411015g7bbe315df2b0bb56@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0803061557320.7660@fbirervta.pbzchgretzou.qr>
On Fri, Mar 7, 2008 at 1:48 AM, Jan Engelhardt <jengelh@computergmbh.de> wrote:
> Hello everyone,
>
>
> I spent the last two days writing a text-based tree visualizer;
> gitk is really convenient, but unfortunately it needs an X display,
> tigs tree view left me unimpressed, and I actually wanted a tool
> that does not read all commits in like gitk/tig do, but just gives me
> the treeview.
>
Here is my view
║ ║ ║ ╟ Merge branch 'jk/portable'
║ ║ ║ ╠═╗
║ ║ ║ ╟ ║ Merge branch 'py/submodule'
║ ║ ║ ╠═╬═╗
║ ║ ║ ╟ ║ ║ Merge branch 'db/diff-to-fp'
║ ║ ║ ╠═╬═╬═╗
║ ║ ║ ╟ ║ ║ ║ Merge branch 'cc/help'
║ ║ ║ ╠═╬═╬═╬═╗
║ ║ ║ ╟ ║ ║ ║ ║ shortlog: do not require to
║ ║ ║ ╟ ║ ║ ║ ║ Merge branch 'maint'
║ ║ ║ ╠═╬═╬═╬═╬═╗
It seems messed up.
--
Ping Yin
next prev parent reply other threads:[~2008-03-17 13:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 17:48 [announce] text-based tree visualizer Jan Engelhardt
2008-03-06 18:24 ` Johannes Schindelin
2008-03-06 18:49 ` Jan Engelhardt
2008-03-06 19:46 ` Johannes Schindelin
2008-03-06 20:46 ` Jonas Fonseca
2008-03-06 20:14 ` David Brown
2008-03-06 20:38 ` Jan Engelhardt
2008-03-07 0:46 ` Miklos Vajna
2008-03-07 13:45 ` Jakub Narebski
2008-03-08 15:01 ` Jan Engelhardt
2008-03-09 12:36 ` Jakub Narebski
2008-03-17 13:40 ` Ping Yin [this message]
2008-03-17 16:27 ` Jan Engelhardt
2008-03-18 0:26 ` Ping Yin
2008-03-18 2:08 ` Jan Engelhardt
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=46dff0320803170640g52411015g7bbe315df2b0bb56@mail.gmail.com \
--to=pkufranky@gmail.com \
--cc=git@vger.kernel.org \
--cc=jengelh@computergmbh.de \
/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).