From: "Harald Nordgren via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Harald Nordgren <haraldnordgren@gmail.com>,
Harald Nordgren <haraldnordgren@gmail.com>
Subject: [PATCH] range-diff: add --matched-only to skip one-sided commits
Date: Fri, 11 Sep 2026 16:41:17 +0000 [thread overview]
Message-ID: <pull.2401.git.git.1789144877632.gitgitgadget@gmail.com> (raw)
From: Harald Nordgren <haraldnordgren@gmail.com>
Reviewing a range-diff often means scrolling past commits that were
simply added or dropped, when only the ones that correspond between
the two ranges are of interest.
--left-only and --right-only already each suppress one of those
one-sided groups, so give --matched-only its own name for applying
both suppressions at once instead of documenting the combination of
two options whose names read as contradictory together. Internally it
just sets both flags, reusing the existing suppression logic in
show_range_diff().
Extend the existing '--left-only'/'--right-only' conflict check in
show_range_diff() to also reject any combination with --matched-only,
since all three narrow the output in ways that cannot be combined.
Signed-off-by: Harald Nordgren <haraldnordgren@gmail.com>
---
range-diff: add --matched-only to skip one-sided commits
Add git range-diff --matched-only to only show commits that correspond
between the two ranges, skipping ones that were only added or only
removed.
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-2401%2FHaraldNordgren%2Frange-diff-matched-only-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-2401/HaraldNordgren/range-diff-matched-only-v1
Pull-Request: https://github.com/git/git/pull/2401
Documentation/git-range-diff.adoc | 10 ++++-
builtin/range-diff.c | 5 ++-
range-diff.c | 11 +++++-
range-diff.h | 2 +-
t/t3206-range-diff.sh | 63 +++++++++++++++++++++++++++++++
5 files changed, 86 insertions(+), 5 deletions(-)
diff --git a/Documentation/git-range-diff.adoc b/Documentation/git-range-diff.adoc
index 5cc5e2ed56..58e59e8e3b 100644
--- a/Documentation/git-range-diff.adoc
+++ b/Documentation/git-range-diff.adoc
@@ -10,7 +10,8 @@ SYNOPSIS
[synopsis]
git range-diff [--color=[<when>]] [--no-color] [<diff-options>]
[--no-dual-color] [--creation-factor=<factor>]
- [--left-only | --right-only] [--diff-merges=<format>]
+ [--left-only | --right-only | --matched-only]
+ [--diff-merges=<format>]
[--remerge-diff] [--no-notes | --notes[=<ref>]]
( <range1> <range2> | <rev1>...<rev2> | <base> <rev1> <rev2> )
[[--] <path>...]
@@ -82,6 +83,13 @@ to revert to color all lines according to the outer diff markers
Suppress commits that are missing from the second specified range
(or the "right range" when using the `<rev1>...<rev2>` form).
+`--matched-only`::
+ Only emit commits that have a corresponding commit in the other
+ range, suppressing any commit that exists on only one side. This is
+ the same as using `--left-only` and `--right-only` together. Useful
+ to skip added or removed commits when reviewing how the commits
+ that survived a rebase changed.
+
`--diff-merges=<format>`::
Instead of ignoring merge commits, generate diffs for them using the
corresponding `--diff-merges=<format>` option of linkgit:git-log[1],
diff --git a/builtin/range-diff.c b/builtin/range-diff.c
index e54c0f7fe1..8059f92eaa 100644
--- a/builtin/range-diff.c
+++ b/builtin/range-diff.c
@@ -46,7 +46,7 @@ int cmd_range_diff(int argc,
.diffopt = &diffopt,
.log_arg = &log_arg
};
- int simple_color = -1, left_only = 0, right_only = 0;
+ int simple_color = -1, left_only = 0, right_only = 0, matched_only = 0;
struct option range_diff_options[] = {
OPT_INTEGER(0, "creation-factor",
&range_diff_opts.creation_factor,
@@ -68,6 +68,8 @@ int cmd_range_diff(int argc,
N_("only emit output related to the first range")),
OPT_BOOL(0, "right-only", &right_only,
N_("only emit output related to the second range")),
+ OPT_BOOL(0, "matched-only", &matched_only,
+ N_("only emit commits that have a corresponding commit in the other range")),
OPT_END()
};
struct option *options;
@@ -186,6 +188,7 @@ int cmd_range_diff(int argc,
range_diff_opts.dual_color = simple_color < 1;
range_diff_opts.left_only = left_only;
range_diff_opts.right_only = right_only;
+ range_diff_opts.matched_only = matched_only;
res = show_range_diff(range1.buf, range2.buf, &range_diff_opts);
strvec_clear(&log_arg);
diff --git a/range-diff.c b/range-diff.c
index 8e2dd2eb19..fa895f5760 100644
--- a/range-diff.c
+++ b/range-diff.c
@@ -591,8 +591,15 @@ int show_range_diff(const char *range1, const char *range2,
struct string_list branch2 = STRING_LIST_INIT_DUP;
unsigned int include_merges = range_diff_opts->include_merges;
- if (range_diff_opts->left_only && range_diff_opts->right_only)
- res = error(_("options '%s' and '%s' cannot be used together"), "--left-only", "--right-only");
+ if (range_diff_opts->left_only + range_diff_opts->right_only +
+ range_diff_opts->matched_only > 1)
+ res = error(_("options '%s', '%s', or '%s' cannot be used together"),
+ "--left-only", "--right-only", "--matched-only");
+
+ if (range_diff_opts->matched_only) {
+ range_diff_opts->left_only = 1;
+ range_diff_opts->right_only = 1;
+ }
if (!res && read_patches(range1, &branch1, range_diff_opts->log_arg, include_merges))
res = error(_("could not parse log for '%s'"), range1);
diff --git a/range-diff.h b/range-diff.h
index 9b70a80009..effd10b9b8 100644
--- a/range-diff.h
+++ b/range-diff.h
@@ -19,7 +19,7 @@
struct range_diff_options {
int creation_factor;
unsigned dual_color:1;
- unsigned left_only:1, right_only:1;
+ unsigned left_only:1, right_only:1, matched_only:1;
unsigned include_merges:1;
size_t max_memory;
const struct diff_options *diffopt; /* may be NULL */
diff --git a/t/t3206-range-diff.sh b/t/t3206-range-diff.sh
index ef92704de3..f85fd0c4ad 100755
--- a/t/t3206-range-diff.sh
+++ b/t/t3206-range-diff.sh
@@ -860,6 +860,69 @@ test_expect_success '--left-only/--right-only' '
test_cmp expect actual
'
+test_expect_success '--left-only, --right-only and --matched-only are incompatible' '
+ test_must_fail git range-diff --left-only --right-only ...common 2>err &&
+ test_grep "cannot be used together" err &&
+
+ test_must_fail git range-diff --left-only --matched-only ...common 2>err &&
+ test_grep "cannot be used together" err &&
+
+ test_must_fail git range-diff --right-only --matched-only ...common 2>err &&
+ test_grep "cannot be used together" err &&
+
+ test_must_fail git range-diff --left-only --right-only --matched-only \
+ ...common 2>err &&
+ test_grep "cannot be used together" err
+'
+
+test_expect_success '--left-only, --right-only and --matched-only each suppress one-sided commits' '
+ test_create_repo matched-only &&
+ (
+ cd matched-only &&
+ git switch --orphan combined-old &&
+ test_commit c-first &&
+ test_commit c-old-only &&
+ test_commit c-common &&
+ git switch -C combined-new c-first &&
+ test_commit c-new-only &&
+ git cherry-pick c-common &&
+
+ old_only_oid=$(git rev-parse --short=7 c-old-only) &&
+ new_only_oid=$(git rev-parse --short=7 c-new-only) &&
+ common_old_oid=$(git rev-parse --short=7 c-common) &&
+ common_new_oid=$(git rev-parse --short=7 HEAD) &&
+
+ git range-diff -s --abbrev=7 combined-old...combined-new >actual &&
+ cat >expect <<-EOF &&
+ 1: $old_only_oid < -: ------- c-old-only
+ -: ------- > 1: $new_only_oid c-new-only
+ 2: $common_old_oid = 2: $common_new_oid c-common
+ EOF
+ test_cmp expect actual &&
+
+ git range-diff -s --abbrev=7 --left-only combined-old...combined-new \
+ >actual &&
+ cat >expect <<-EOF &&
+ 1: $old_only_oid < -: ------- c-old-only
+ 2: $common_old_oid = 2: $common_new_oid c-common
+ EOF
+ test_cmp expect actual &&
+
+ git range-diff -s --abbrev=7 --right-only combined-old...combined-new \
+ >actual &&
+ cat >expect <<-EOF &&
+ -: ------- > 1: $new_only_oid c-new-only
+ 2: $common_old_oid = 2: $common_new_oid c-common
+ EOF
+ test_cmp expect actual &&
+
+ git range-diff -s --abbrev=7 --matched-only combined-old...combined-new \
+ >actual &&
+ echo "2: $common_old_oid = 2: $common_new_oid c-common" >expect &&
+ test_cmp expect actual
+ )
+'
+
test_expect_success 'ranges with pathspecs' '
git range-diff topic...mode-only-change -- other-file >actual &&
test_line_count = 2 actual &&
base-commit: fa7f9290efe2bd22dd736689597b474b93798e11
--
gitgitgadget
next reply other threads:[~2026-09-11 16:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 16:41 Harald Nordgren via GitGitGadget [this message]
2026-09-11 17:19 ` [PATCH] range-diff: add --matched-only to skip one-sided commits Junio C Hamano
2026-09-11 18:48 ` Harald Nordgren
2026-09-11 18:52 ` Junio C Hamano
2026-09-11 19:01 ` Harald Nordgren
2026-09-11 19:05 ` Junio C Hamano
2026-09-11 20:55 ` [PATCH v2] " Harald Nordgren via GitGitGadget
2026-09-14 16:33 ` Junio C Hamano
2026-09-15 7:51 ` [PATCH v3] " Harald Nordgren via GitGitGadget
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=pull.2401.git.git.1789144877632.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=haraldnordgren@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;
as well as URLs for NNTP newsgroup(s).