public inbox for git@vger.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Toon Claes <toon@iotcl.com>
Cc: Johannes Sixt <j6t@kdbg.org>,  git@vger.kernel.org
Subject: Re: [PATCH RFC] graph: implement git-log(1) --untangle
Date: Mon, 09 Feb 2026 11:35:51 -0800	[thread overview]
Message-ID: <xmqqecmt4smg.fsf@gitster.g> (raw)
In-Reply-To: <87h5rqqv4y.fsf@iotcl.com> (Toon Claes's message of "Mon, 09 Feb 2026 07:38:21 +0100")

Toon Claes <toon@iotcl.com> writes:

> I've been thinking about something else. Display in some way part of the
> history is missing, maybe by showing a '.' in the graph:
>
>     *
>     |\
>     | *
>     | *
>     | .
>     *
>     |\
>     * *
>     |/
>     *
>     *
>
> This indicates a piece of the history is truncated. I'm still on the
> fence about this

It has been quite a while since I used gitk the last time, but I
recall it did something similar.  Instead of saying "I removed line
from here so you do not know where the other end of it is", it drew
a little down arrow and there was some way to find the matching up
arrow further down in the graph (either being in the same color or
perhaps clicking on one end jumped you to the other one, taking
advantage of being interactive program, I do not recall the
details).  I wnder if we can "label" your "." above with something
like (a)..(z)(aa)..(az).. or something?

      parent reply	other threads:[~2026-02-09 19:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-06 18:49 [PATCH RFC] graph: implement git-log(1) --untangle Toon Claes
2026-02-06 21:27 ` Junio C Hamano
2026-02-09  6:19   ` Toon Claes
2026-02-07  9:32 ` Johannes Sixt
2026-02-09  6:38   ` Toon Claes
2026-02-09 16:39     ` Johannes Sixt
2026-02-09 19:35     ` Junio C Hamano [this message]

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=xmqqecmt4smg.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=j6t@kdbg.org \
    --cc=toon@iotcl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox