From: Pablo Sabater <pabloosabaterr@gmail.com>
To: git@vger.kernel.org
Cc: christian.couder@gmail.com, karthik.188@gmail.com,
jltobler@gmail.com, ayu.chandekar@gmail.com,
siddharthasthana31@gmail.com, chandrapratap3519@gmail.com,
gitster@pobox.com, j6t@kdbg.org, szeder.dev@gmail.com,
Pablo Sabater <pabloosabaterr@gmail.com>
Subject: [GSoC PATCH v6 3/3] graph: add truncation mark to capped lanes
Date: Sat, 28 Mar 2026 01:11:13 +0100 [thread overview]
Message-ID: <20260328001113.1275291-4-pabloosabaterr@gmail.com> (raw)
In-Reply-To: <20260328001113.1275291-1-pabloosabaterr@gmail.com>
When lanes are hidden by --graph-lane-limit, show a "~"
truncation mark, so users know that there are lanes
being truncated. The "~" is chosen because it is not
used elsewhere in the graph and it is discrete.
Signed-off-by: Pablo Sabater <pabloosabaterr@gmail.com>
---
Documentation/rev-list-options.adoc | 5 ++-
graph.c | 22 +++++++---
t/t4215-log-skewed-merges.sh | 64 ++++++++++++++---------------
3 files changed, 52 insertions(+), 39 deletions(-)
diff --git a/Documentation/rev-list-options.adoc b/Documentation/rev-list-options.adoc
index 1b6ea89a63..937ffc6195 100644
--- a/Documentation/rev-list-options.adoc
+++ b/Documentation/rev-list-options.adoc
@@ -1261,8 +1261,9 @@ This implies the `--topo-order` option by default, but the
`--graph-lane-limit=<n>`::
When `--graph` is used, limit the number of graph lanes to be shown.
- Lanes over the limit are not shown. By default it is set to 0
- (no limit), zero and negative values are ignored and treated as no limit.
+ Lanes over the limit are replaced with a truncation mark '~'.
+ By default it is set to 0 (no limit), zero and negative values
+ are ignored and treated as no limit.
ifdef::git-rev-list[]
`--count`::
diff --git a/graph.c b/graph.c
index ee1f9e2d2d..842282685f 100644
--- a/graph.c
+++ b/graph.c
@@ -706,11 +706,11 @@ static void graph_update_columns(struct git_graph *graph)
}
/*
- * If graph_max_lanes is set, cap the width
+ * If graph_max_lanes is set, cap the width
*/
if (graph->revs->graph_max_lanes > 0) {
/*
- * Width is column index while a lane is half that.
+ * width of "| " per lanes plus truncation mark "~ ".
* Allow commits from merges to align to the merged lane.
*/
int max_width = graph->revs->graph_max_lanes * 2 + 2;
@@ -868,8 +868,10 @@ static void graph_output_padding_line(struct git_graph *graph,
* Output a padding row, that leaves all branch lines unchanged
*/
for (i = 0; i < graph->num_new_columns; i++) {
- if (graph_needs_truncation(graph, i))
+ if (graph_needs_truncation(graph, i)) {
+ graph_line_addstr(line, "~ ");
break;
+ }
graph_line_write_column(line, &graph->new_columns[i], '|');
graph_line_addch(line, ' ');
}
@@ -928,6 +930,7 @@ static void graph_output_pre_commit_line(struct git_graph *graph,
graph_line_write_column(line, col, '|');
graph_line_addchars(line, ' ', graph->expansion_row);
} else if (seen_this && graph_needs_truncation(graph, i)) {
+ graph_line_addstr(line, "~ ");
break;
} else if (seen_this && (graph->expansion_row == 0)) {
/*
@@ -1025,8 +1028,10 @@ static void graph_draw_octopus_merge(struct git_graph *graph, struct graph_line
* Commit is at commit_index, each iteration move one lane to
* the right from the commit.
*/
- if (graph_needs_truncation(graph, graph->commit_index + 1 + i))
+ if (graph_needs_truncation(graph, graph->commit_index + 1 + i)) {
+ graph_line_addstr(line, "~ ");
break;
+ }
graph_line_write_column(line, col, (i == dashed_parents - 1) ? '.' : '-');
}
@@ -1070,6 +1075,7 @@ static void graph_output_commit_line(struct git_graph *graph, struct graph_line
if (graph->num_parents > 2)
graph_draw_octopus_merge(graph, line);
} else if (graph_needs_truncation(graph, i)) {
+ graph_line_addstr(line, "~ ");
seen_this = 1;
break;
} else if (seen_this && (graph->edges_added > 1)) {
@@ -1203,6 +1209,7 @@ static void graph_output_post_merge_line(struct git_graph *graph, struct graph_l
j / 2 + i <= graph->num_columns) {
if ((j + i * 2) % 2 != 0)
graph_line_addch(line, ' ');
+ graph_line_addstr(line, "~ ");
truncated = 1;
break;
}
@@ -1214,6 +1221,7 @@ static void graph_output_post_merge_line(struct git_graph *graph, struct graph_l
*/
if (graph_needs_truncation(graph, (j + 1) / 2 + i) &&
j < graph->num_parents - 1) {
+ graph_line_addstr(line, "~ ");
truncated = 1;
break;
} else if (graph->edges_added > 0 || j < graph->num_parents - 1)
@@ -1228,6 +1236,7 @@ static void graph_output_post_merge_line(struct git_graph *graph, struct graph_l
if (graph->edges_added == 0)
graph_line_addch(line, ' ');
} else if (graph_needs_truncation(graph, i)) {
+ graph_line_addstr(line, "~ ");
break;
} else if (seen_this) {
if (graph->edges_added > 0)
@@ -1388,6 +1397,7 @@ static void graph_output_collapsing_line(struct git_graph *graph, struct graph_l
int target = graph->mapping[i];
if (!truncated && graph_needs_truncation(graph, i / 2)) {
+ graph_line_addstr(line, "~ ");
truncated = 1;
}
@@ -1487,8 +1497,10 @@ static void graph_padding_line(struct git_graph *graph, struct strbuf *sb)
for (i = 0; i < graph->num_columns; i++) {
struct column *col = &graph->columns[i];
- if (graph_needs_truncation(graph, i))
+ if (graph_needs_truncation(graph, i)) {
+ graph_line_addstr(&line, "~ ");
break;
+ }
graph_line_write_column(&line, col, '|');
diff --git a/t/t4215-log-skewed-merges.sh b/t/t4215-log-skewed-merges.sh
index d7524e9366..1612f05f1b 100755
--- a/t/t4215-log-skewed-merges.sh
+++ b/t/t4215-log-skewed-merges.sh
@@ -376,9 +376,9 @@ test_expect_success 'log --graph --graph-lane-limit=2 limited to two lanes' '
|\ \
| | * 7_G
| | * 7_F
- | * 7_E
- | * 7_D
- * | 7_C
+ | * ~ 7_E
+ | * ~ 7_D
+ * | ~ 7_C
| |/
|/|
* | 7_B
@@ -389,16 +389,16 @@ test_expect_success 'log --graph --graph-lane-limit=2 limited to two lanes' '
test_expect_success 'log --graph --graph-lane-limit=1 truncate mid octopus merge' '
check_graph --graph-lane-limit=1 M_7 <<-\EOF
- *- 7_M4
- |\
- | 7_G
- | 7_F
+ *-~ 7_M4
+ |\~
+ | ~ 7_G
+ | ~ 7_F
| * 7_E
| * 7_D
- * 7_C
- |
- |/
- * 7_B
+ * ~ 7_C
+ | ~
+ |/~
+ * ~ 7_B
|/
* 7_A
EOF
@@ -411,24 +411,24 @@ test_expect_success 'log --graph --graph-lane-limit=3 limited to three lanes' '
| | * 7_M2
| | |\
| | | * 7_H
- | | | 7_M3
- | | | 7_J
- | | | 7_I
- | | | 7_M4
- | |_|_
- |/| |
- | | |_
- | |/|
- | | |
- | | |/
- | | * 7_G
- | | |
- | | |/
- | | * 7_F
- | * | 7_E
- | | |/
- | |/|
- | * | 7_D
+ | | | ~ 7_M3
+ | | | ~ 7_J
+ | | | ~ 7_I
+ | | | ~ 7_M4
+ | |_|_~
+ |/| | ~
+ | | |_~
+ | |/| ~
+ | | | ~
+ | | |/~
+ | | * ~ 7_G
+ | | | ~
+ | | |/~
+ | | * ~ 7_F
+ | * | ~ 7_E
+ | | |/~
+ | |/| ~
+ | * | ~ 7_D
| | |/
| |/|
* | | 7_C
@@ -452,9 +452,9 @@ test_expect_success 'log --graph --graph-lane-limit=6 check if it only shows fir
| | | | | * 7_J
| | | | * | 7_I
| | | | | | * 7_M4
- | |_|_|_|_|/
- |/| | | | |/
- | | |_|_|/|
+ | |_|_|_|_|/~
+ |/| | | | |/~
+ | | |_|_|/| ~
| |/| | | |/
| | | |_|/|
| | |/| | |
--
2.43.0
prev parent reply other threads:[~2026-03-28 0:11 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 13:34 [GSoC RFC PATCH] graph: add --graph-max option to limit displayed columns Pablo Sabater
2026-03-16 17:04 ` Karthik Nayak
2026-03-16 19:48 ` Pablo
2026-03-17 22:09 ` [GSoC RFC PATCH v2] graph: add --max-columns " Pablo Sabater
2026-03-18 16:05 ` Junio C Hamano
2026-03-18 18:20 ` Pablo
2026-03-19 7:07 ` Johannes Sixt
2026-03-22 19:54 ` [GSoC PATCH WIP RFC v3 0/3] graph: add --graph-lane-limit option Pablo Sabater
2026-03-22 20:37 ` [GSoC PATCH WIP RFC v3 1/3] " Pablo Sabater
2026-03-22 20:38 ` [GSoC PATCH WIP RFC v3 2/3] graph: truncate graph visual output Pablo Sabater
2026-03-22 20:38 ` [GSoC PATCH WIP RFC v3 3/3] graph: add documentation and testing about --graph-lane-limit Pablo Sabater
2026-03-22 22:09 ` [GSoC PATCH WIP RFC v3 1/3] graph: add --graph-lane-limit option Junio C Hamano
2026-03-23 2:33 ` Pablo
2026-03-23 21:59 ` [GSoC PATCH v4 0/3] " Pablo Sabater
2026-03-23 21:59 ` [GSoC PATCH v4 1/3] " Pablo Sabater
2026-03-25 7:02 ` SZEDER Gábor
2026-03-25 10:03 ` Johannes Sixt
2026-03-25 12:29 ` Pablo
2026-03-23 21:59 ` [GSoC PATCH v4 2/3] graph: truncate graph visual output Pablo Sabater
2026-03-25 10:04 ` Johannes Sixt
2026-03-25 11:19 ` Pablo
2026-03-23 21:59 ` [GSoC PATCH v4 3/3] graph: add documentation and tests about --graph-lane-limit Pablo Sabater
2026-03-25 10:07 ` Johannes Sixt
2026-03-25 11:49 ` Pablo
2026-03-25 10:02 ` [GSoC PATCH v4 0/3] graph: add --graph-lane-limit option Johannes Sixt
2026-03-25 12:28 ` Pablo
2026-03-25 17:44 ` Johannes Sixt
2026-03-25 17:58 ` Pablo
2026-03-25 17:43 ` [GSoC PATCH v5 0/2] " Pablo Sabater
2026-03-25 17:44 ` [GSoC PATCH v5 1/2] " Pablo Sabater
2026-03-25 22:11 ` Junio C Hamano
2026-03-27 14:22 ` Pablo
2026-03-27 16:07 ` Pablo
2026-03-27 16:34 ` Junio C Hamano
2026-03-25 17:44 ` [GSoC PATCH v5 2/2] graph: add documentation and tests about --graph-lane-limit Pablo Sabater
2026-03-28 0:11 ` [GSoC PATCH v6 0/3] graph: add --graph-lane-limit option Pablo Sabater
2026-03-28 0:11 ` [GSoC PATCH v6 1/3] graph: limit the graph width to a hard-coded max Pablo Sabater
2026-03-28 0:11 ` [GSoC PATCH v6 2/3] graph: add --graph-lane-limit option Pablo Sabater
2026-03-28 0:11 ` Pablo Sabater [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=20260328001113.1275291-4-pabloosabaterr@gmail.com \
--to=pabloosabaterr@gmail.com \
--cc=ayu.chandekar@gmail.com \
--cc=chandrapratap3519@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j6t@kdbg.org \
--cc=jltobler@gmail.com \
--cc=karthik.188@gmail.com \
--cc=siddharthasthana31@gmail.com \
--cc=szeder.dev@gmail.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