All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonas Fonseca <fonseca@diku.dk>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Gitk feature - show nearby tags
Date: Sat, 3 Jun 2006 18:19:01 +0200	[thread overview]
Message-ID: <20060603161900.GA4882@diku.dk> (raw)
In-Reply-To: <e5sa47$qv8$1@sea.gmane.org>

Jakub Narebski <jnareb@gmail.com> wrote Sat, Jun 03, 2006:
> Jonas Fonseca wrote:
> 
> > 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,[...]
> 
> As I can see you use 'vertical' layout. Do I understand correctly that '*'
> refers to commit on marked (by column) branch, and '|' means pass-thru?

Yes, and 'M' marks merges. Putting information in the "commit node"
should make certain things more obvious. You could encode information
such as whether a commit is a "unique head" (nothing other revisions
references this commit). For example the first commit will always be
unique, but when using --all other heads might show up "unique".

	+ [master] ...
	* ...
	| + [unmerged/topic] ...
	| * ...
	*' ...

> BTW. you might want to take a look at http://revctrl.org/ diagrams;
> AFAICT all the git documentation uses 'horizontal' layout, which is good
> for example but perhaps not for long-lived development...

Looking at the examples on http://revctrl.org/StaircaseMerge: it might
be more readable but not as dense as I would like, namely one commit pr
line.

-- 
Jonas Fonseca

  reply	other threads:[~2006-06-03 16:19 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
2006-06-03 15:33     ` Jakub Narebski
2006-06-03 16:19       ` Jonas Fonseca [this message]
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=20060603161900.GA4882@diku.dk \
    --to=fonseca@diku.dk \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.