From: Matt Hunter Date: Tue, 03 Nov 2026 00:01:10 GMT Subject: Re: [PATCH v3] range-diff: add --matched-only to skip one-sided commits Message-ID: In-Reply-To: On Mon Nov 2, 2026 at 4:15 PM EST, Harald Nordgren wrote: >> On Mon, Nov 2, 2026 at 5:47 PM Ben Knoble wrote: >> > >> > Anyway, I’d be curious >> > to learn what motivated Harald, as it might be useful to my >> > own workflows, in which case I might be able to review more. >> >> For me, it's simple: >> >> If we take this branch, and I do some other changes, and then rebase >> against the latest master. Then when I run >> >> git range-diff >> pr-git-2401/HaraldNordgren/range-diff-matched-only-v3...range-diff-matched-only >> >> I will have to scroll through 311 unrelated commits before I can see >> what I actually changed. I want those gone. >> >> ``` >> -: ---------- > 282: b2608c4076 t2104: avoid suppressing git's exit code >> -: ---------- > 283: 5e106cb22b pack-write: make index-pack output >> comment hash agnostic >> [...] >> -: ---------- > 311: ebdc087dc9 The 13th batch >> 1: ee195c14fc = 312: f01d7e30ef range-diff: add --matched-only to >> skip one-sided commits >> ``` >> > Well, in this particular case `--left-only` solves it. > > So maybe that's enough. Wouldn't invoking as git range-diff origin/master pr-git-2401/HaraldNordgren/range-diff-matched-only-v3 range-diff-matched-only address this case?