Re: [PATCH v3] range-diff: add --matched-only to skip one-sided commits
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Nov 2, 2026, 09:21 UTC
- Message-ID
- <xmqqy0bblhbp.fsf@gitster.g>
- In-Reply-To
- <pull.2401.v3.git.git.1789458703432.gitgitgadget@gmail.com>
"Harald Nordgren via GitGitGadget" <gitgitgadget@gmail.com> writes:
Show 29 quoted lines
> 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, but they are defined as "only show this side" and > so cannot be given together, which is exactly why show_range_diff() > already rejected that combination. Give the "show only the commits > that correspond on both sides" behavior its own name, --matched-only, > instead of asking users to reach for a combination that errors out. > > Extend the existing '--left-only'/'--right-only' conflict check 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. > > Changes in v2: > > * Update docs and commit message. > * Use die_for_incompatible_opt3.
This is more than 6 weeks old and looking at the archive, nobody (including me) was really interested in the topic. Anybody wants to take a fresh look at the topic?
Unless we see some volunteers to give it a review in a few weeks, I will discard the topic out of my tree, as 'seen' has been crowded with topics that have been collecting dust without getting many reviews.
Thanks.