From: Jonas Fonseca <fonseca@diku.dk>
To: Junio C Hamano <junkio@cox.net>
Cc: Paul Mackerras <paulus@samba.org>, git@vger.kernel.org
Subject: Re: Gitk feature - show nearby tags
Date: Sat, 3 Jun 2006 17:12:40 +0200 [thread overview]
Message-ID: <20060603151240.GA4024@diku.dk> (raw)
In-Reply-To: <7vslmm8rcd.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> wrote Sat, Jun 03, 2006:
> For a graphical interface like gitk it may not be such a big
> deal (you can always follow the line), but an interface like tig
> that shows commits in a linear fashion it would make a big
> difference in usability.
I already took your hint from the other day on irc and have begun on
implementing this revision graph visualization for tig. :)
The problem is of course to come up with some ascii-art which is both
readable and dense. Below is my mockup of something not using line
graphics, however using line graphics it might be possible to get
something more unambiguos but also more "edgy".
* [release] Sync docs
M Merge ...
|`* [master] Fix spelling
| * Implement ...
M | Merge ...
|`M Merge ...
| |`* Topic B ...
| | * Topic B ...
| * | Topic A
| * | Topic A
| *' Update docs
: :
M | Merge ...
|`M Merge ...
| *`. Topic B ...
| * | Topic B ...
| | * Topic A
| | * Topic A
| *' Update docs
: :
M | Merge ...
|`M Merge ...
| *`. Topic B ...
| * | Topic B ...
| | * Topic A
M `.`. Merge
|`* | | Update docs
--
Jonas Fonseca
next prev parent reply other threads:[~2006-06-03 15:12 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-03 9:38 Gitk feature - show nearby tags Paul Mackerras
2006-06-03 10:29 ` Junio C Hamano
2006-06-03 11:16 ` Marco Costalba
2006-06-04 1:59 ` Paul Mackerras
2006-06-04 7:08 ` Marco Costalba
2006-06-04 9:25 ` Junio C Hamano
2006-06-04 9:40 ` Marco Costalba
2006-06-04 9:21 ` Junio C Hamano
2006-06-04 9:54 ` Marco Costalba
2006-06-04 10:06 ` Junio C Hamano
2006-06-04 10:10 ` Junio C Hamano
2006-06-04 10:33 ` Marco Costalba
2006-06-04 10:42 ` Marco Costalba
2006-06-04 10:42 ` Junio C Hamano
2006-06-04 13:57 ` Marco Costalba
2006-06-05 6:20 ` Junio C Hamano
2006-06-05 11:54 ` Marco Costalba
2006-06-03 12:23 ` Paul Mackerras
2006-06-03 16:50 ` Junio C Hamano
2006-06-04 1:51 ` Paul Mackerras
2006-06-03 15:12 ` Jonas Fonseca [this message]
2006-06-03 15:33 ` Jakub Narebski
2006-06-03 16:19 ` Jonas Fonseca
2006-06-04 20:58 ` Junio C Hamano
2006-06-05 0:04 ` Jonas Fonseca
2006-06-05 1:37 ` Junio C Hamano
2006-06-05 20:08 ` Junio C Hamano
2006-06-05 20:19 ` Jonas Fonseca
2006-06-05 21:11 ` Jonas Fonseca
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=20060603151240.GA4024@diku.dk \
--to=fonseca@diku.dk \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=paulus@samba.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).