Re: [PATCH v9 0/4] graph: indent visual roots in graph

>
> On Sat, Jul 11, 2026 at 05:41:58PM +0200, Pablo Sabater wrote:
> > I think that this solves an ambiguity so it should be the default option
> > and someone who doesn't want the indentation has to explicitly unset it
> > maybe with something like '--no-graph-indent'.
>
> The reason I prefer the current way of printing as the default is
> because the ambiguity arises only when each commit occupies exactly one
> line. In any other case we can clearly see the edges connecting the
> vertices. I'd rather have --oneline imply what would be --graph-indent
> instead of having to pass --no-graph-indent on any other format
> different from --oneline or --format=reference.

> > Apart from having an option to disable indentation.
> >
> > We could have the cascading to have a limit or make it zig-zag:
> >
> > instead of:
> >
> > A
> >   B
> >     C
> >       D
> >
> > We could do:
> >
> > A
> >   B
> > C
> >   D
> >
> > This would have its own edge cases like:
> >
> > A
> >   B
> > C <- if we zig-zag here C and D become ambiguous, currently we are
> > D    indenting only the last commits (visual roots) here we would have
> > D    to chose between continuing cascading or indenting the first of D.
> >
> > I'm not so sure if I like the zig-zag solution because we need to think again
> > if it causes an ambiguity, but I wanted to mention it.
> >
> > I think we need some more opinions about the design.
>
> I don't dislike the the current solution but I can see it degenerating
> if someone contributes a lot of one-patch series.
>
> Maybe you could indent commits that are both head and tail up to two
> levels and then on the third go back to the beginning of the line. That
> way you kind of have a zig-zag but without ambiguity. You'd only have to
> add a counter to keep track of the level of indentation.