From: Junio C Hamano <gitster@pobox.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: "Antoine Beaupré" <anarcat@koumbit.org>, git@vger.kernel.org
Subject: Re: [PATCH] graph.c: visual difference on subsequent series
Date: Thu, 03 Sep 2015 10:13:47 -0700 [thread overview]
Message-ID: <xmqq613rl92s.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <55E7FEF3.2020400@drmicha.warpmail.net> (Michael J. Gruber's message of "Thu, 3 Sep 2015 10:04:03 +0200")
Michael J Gruber <git@drmicha.warpmail.net> writes:
>> Is the design of your independent implementation the same except
>> that 'o' is used instead of 'x'? Independent implementation does
>> not make the same design magically better, if that is the case ;-)
>
> Interestingly, the patch to the tests lists * to o changes only, no < or
>> to o.
Well, in that case, then the opposite but an equivalent problem
exists in the design, no? It promises to make roots stand out by
painting them as 'o', but it sometimes fails to do so. In other
words, ...
> The reason is simply that the patch doesn't change anything for left nor
> right commits. I would say that is the best compromise since it does not
> change the overall layout, provides more information by default and does
> not override information that is requested specifically.
... it fails your last criteria.
> If we want to put more information into log --graph simultaneously we
> should really go beyond ASCII and look at how tig does it, e.g. using
> unicode characters.
That's another way to do so, but shifting columns to show where the
history is not connected also does not change the overall layout,
provides more information by default, etc., and a big plus is that
it would be an approach to do so without having to go beyond ASCII.
next prev parent reply other threads:[~2015-09-03 17:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 13:33 [PATCH] graph.c: visual difference on subsequent series Antoine Beaupré
2015-07-27 19:37 ` Antoine Beaupré
2015-07-27 20:17 ` Junio C Hamano
2015-09-03 8:04 ` Michael J Gruber
2015-09-03 17:13 ` Junio C Hamano [this message]
2015-09-04 14:07 ` Michael J Gruber
2015-09-04 16:08 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2013-10-25 20:51 Milton Soares Filho
2013-10-25 16:07 Milton Soares Filho
2013-10-25 17:13 ` Junio C Hamano
2013-10-25 20:49 ` Milton Soares Filho
2013-10-26 2:37 ` Keshav Kini
2013-10-28 15:41 ` Junio C Hamano
2013-10-28 16:59 ` Keshav Kini
2013-10-28 17:18 ` Milton Soares Filho
2013-10-28 17:39 ` Junio C Hamano
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=xmqq613rl92s.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=anarcat@koumbit.org \
--cc=git@drmicha.warpmail.net \
--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 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.