git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [GSoC PATCH v6 0/3] graph: add --graph-lane-limit option

From
Pablo <pabloosabaterr@gmail.com>
Date
Apr 3, 2026, 19:13 UTC
Message-ID
<CAN5EUNQbdoymmJcqzqzUy2aEKg-qUBqe_7bSmWwboJ4PoCfFJQ@mail.gmail.com>
In-Reply-To
<dc134cdb-cdc3-4c54-a97e-993a26900d0d@gmail.com>
El vie, 3 abr 2026 a las 20:56, Tian Yuchen (<a3205153416@gmail.com>) escribió:
Show 42 quoted lines
>
>
> I have some reservations about this idea, although I know little about
> the graph engine. ;)
>
> In terms of user conventions, in --graph, '/' and '\' represent
> branching and merging respectively. Here, however, the '/' used to break
> up between different root commits is merely a placeholder and has no
> specific meaning. I feel that this not only goes against user intuition
> but also creates visual confusion: (I just drew this off the cuff, but I
> reckon it should look something like this?)
>
> > * (main) commit 4
> > | * (feature) commit 4
> > | | * (doc1) commit
> > | | * (doc1) root
> > | |   * (main) commit 3
> > | |  /|
> > | * | (feature) commit 3
> > | |/
> > | * (doc2) root
> > |   * (main) commit 2
> > |  /
> > * (feature) commit 2
> > | * (main) commit 1
>
> I don’t know about you, but I find this rather difficult to grasp. At
> the very least, I can’t tell at a glance where the actual merges and
> branches are. I don’t think a good solution should involve shifting left
> or right. Perhaps it would be better to use a special symbol in the root
> commit (such as the ■ symbol, which resembles a full stop? People would
> instinctively recognise it as a terminator):
>
> |* (main) commit 2
> | * (feature) commit 2
> | ■ (doc1) ROOT COMMIT
> * | (main) commit 1
>
> (I wonder if there might be any character compatibility issues. Anyway,
> I like square characters. Square things are all rather cute.)
>
> Regards, Yuchen

Hi Yuchen, even tho we have diverged a little, this thread is for a new option to limit the graph horizontally, see the cover letter. It's currently being held, waiting for a RFC about column rearrangements. But I'm attempting the root commits issue before.

But what Junio mentioned is actually interesting and it's being
discussed currently in a new thread, to avoid having two different
topics here.
at :
  https://lore.kernel.org/git/20260402211717.3604688-1-pabloosabaterr@gmail.com/
This seems to have been attempted multiple times and the idea to have
a new symbol was thought of already.
at:
  https://lore.kernel.org/git/191201d6eaa3$4b585fa0$e2091ee0$@pdinc.us/
from the same thread, but remarkable (part of the review from junio in
the new thread):
  https://lore.kernel.org/git/xmqqwnwajbuj.fsf@gitster.c.googlers.com/

I already have some feedback and I'll send a v2 later today or maybe tomorrow, BUT testing and thoughts about it are very welcome, so feel free. Pablo.

Previous: Tian YuchenNext: Junio C Hamano
Message 47 of 48 in “graph: add --graph-max option to limit displayed columns”
  1. graph: add --graph-max option to limit displayed columnsPablo Sabater, Mar 16, 2026
  2. Karthik NayakMar 16, 2026
  3. PabloMar 16, 2026
  4. graph: add --max-columns option to limit displayed columnsPablo Sabater, Mar 17, 2026
  5. Junio C HamanoMar 18, 2026
  6. PabloMar 18, 2026
  7. Johannes SixtMar 19, 2026
  8. 0/3 graph: add --graph-lane-limit optionPablo Sabater, Mar 22, 2026
  9. 1/3 graph: add --graph-lane-limit optionPablo Sabater, Mar 22, 2026
  10. 2/3 graph: truncate graph visual outputPablo Sabater, Mar 22, 2026
  11. 3/3 graph: add documentation and testing about --graph-lane-limitPablo Sabater, Mar 22, 2026
  12. Junio C HamanoMar 22, 2026
  13. PabloMar 23, 2026
  14. 0/3 graph: add --graph-lane-limit optionPablo Sabater, Mar 23, 2026
  15. 1/3 graph: add --graph-lane-limit optionPablo Sabater, Mar 23, 2026
  16. SZEDER GáborMar 25, 2026
  17. Johannes SixtMar 25, 2026
  18. PabloMar 25, 2026
  19. 2/3 graph: truncate graph visual outputPablo Sabater, Mar 23, 2026
  20. Johannes SixtMar 25, 2026
  21. PabloMar 25, 2026
  22. 3/3 graph: add documentation and tests about --graph-lane-limitPablo Sabater, Mar 23, 2026
  23. Johannes SixtMar 25, 2026
  24. PabloMar 25, 2026
  25. Johannes SixtMar 25, 2026
  26. PabloMar 25, 2026
  27. Johannes SixtMar 25, 2026
  28. PabloMar 25, 2026
  29. 0/2 graph: add --graph-lane-limit optionPablo Sabater, Mar 25, 2026
  30. 1/2 graph: add --graph-lane-limit optionPablo Sabater, Mar 25, 2026
  31. Junio C HamanoMar 25, 2026
  32. PabloMar 27, 2026
  33. PabloMar 27, 2026
  34. Junio C HamanoMar 27, 2026
  35. 2/2 graph: add documentation and tests about --graph-lane-limitPablo Sabater, Mar 25, 2026
  36. 0/3 graph: add --graph-lane-limit optionPablo Sabater, Mar 28, 2026
  37. 1/3 graph: limit the graph width to a hard-coded maxPablo Sabater, Mar 28, 2026
  38. 2/3 graph: add --graph-lane-limit optionPablo Sabater, Mar 28, 2026
  39. 3/3 graph: add truncation mark to capped lanesPablo Sabater, Mar 28, 2026
  40. Junio C HamanoMar 31, 2026
  41. Johannes SixtApr 1, 2026
  42. PabloApr 1, 2026
  43. Junio C HamanoApr 1, 2026
  44. PabloApr 2, 2026
  45. Junio C HamanoApr 2, 2026
  46. Tian YuchenApr 3, 2026
  47. PabloApr 3, 2026
  48. Junio C HamanoApr 3, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.