Re: [PATCH] range-diff: add --matched-only to skip one-sided commits
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Sep 11, 2026, 19:05 UTC
- Message-ID
- <xmqqik4ba9sq.fsf@gitster.g>
- In-Reply-To
- <CAHwyqnWVXuDMAonj1jK9687xhjiT4h-0E2qzhjwPXOTKfMhoGQ@mail.gmail.com>
Harald Nordgren <haraldnordgren@gmail.com> writes:
Show 15 quoted lines
>> > Seems like a big change, and deprecated options are a pain in the neck
>> > because we can never actually remove them.
>> >
>> > If we decide to go this way, we might name them "--hide-{left,right}"
>> > and just not introduce a condition that makes them incompatible. Then
>> > "--matched-only" would be pure syntactic sugar and wouldn't even be
>> > 100% necessary to have to achieve this.
>>
>> Or we can just keep the code and fix the documentation. I think
>> that would be much less impact.
>
> I agree.
>
>
> HaraldI thought I'd try my own version, but it seems that we can simply remove the misleading sentence and the remainder already is very easy to read and understand ;-)
`--matched-only`:: Only emit commits that have a corresponding commit in the other range, suppressing any commit that exists on only one side. Useful to skip added or removed commits when reviewing how the commits that survived a rebase changed.