Re: [PATCH v3] range-diff: add --matched-only to skip one-sided commits
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Nov 3, 2026, 00:16 UTC
- Message-ID
- <xmqqcxsmg473.fsf@gitster.g>
- In-Reply-To
- <DML4UIOWA70L.2102KB7HQNX3O@lfurio.us>
"Matt Hunter" <m@lfurio.us> writes:
Show 7 quoted lines
> 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?
Three-rev form where <base> and two evolutions <rev1> and <rev2> are given, and <base>..<rev1> and <base>..<rev2> are compared?
I thought Harald's case was to take the patches from the previous round of the topic and rebase them on top of a different base (e.g., updated origin/master), so there is no suitable single <base> for the three-rev form, but I may have misunderstood his example.