From: Junio C Hamano <gitster@pobox.com>
To: "Antoine Beaupré" <anarcat@koumbit.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] graph.c: visual difference on subsequent series
Date: Mon, 27 Jul 2015 13:17:40 -0700 [thread overview]
Message-ID: <xmqqegjticd7.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <87twspe6ix.fsf@marcos.anarc.at> ("Antoine Beaupré"'s message of "Mon, 27 Jul 2015 15:37:26 -0400")
Antoine Beaupré <anarcat@koumbit.org> writes:
> Any reason why this patch wasn't included / reviewed?
> ...
>> This patch is similar than the one provided by Milton Soares Filho in
>> 1382734287.31768.1.git.send.email.milton.soares.filho@gmail.com but was
>> implemented independently and uses the 'o' character instead of 'x'.
The reason why Milton's patch was not taken after discussion [*1*]
was not because its implementation was poor, but its design was not
good. By overriding '*' '<' or '>' with x, it made it impossible to
distinguish a root on the left side branch and a root on the right
side branch.
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 ;-)
If the design is different, please explain how your patch solves the
issue with Milton's design in your log message.
For example, you could use the column arrangement to solve it, e.g.
History sequence A: a1 -- a2 -- a3 (root-commit)
History sequence B: b1 -- b2 -- b3 (root-commit)
$ git log --graph --oneline A B
* a1
* a2
* a3
* b1
* b2
* b3
$ git log --graph --oneline --left-right A...B
< a1
< a2
< a3
> b1
> b2
> b3
I am not saying that the above would be the only way to do so; there
may be other ways to solve the issue.
[Reference]
*1* http://thread.gmane.org/gmane.comp.version-control.git/236708/focus=236843
next prev parent reply other threads:[~2015-07-27 20:17 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 [this message]
2015-09-03 8:04 ` Michael J Gruber
2015-09-03 17:13 ` Junio C Hamano
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=xmqqegjticd7.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=anarcat@koumbit.org \
--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.