Re: [PATCH v3] range-diff: add --matched-only to skip one-sided commits
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Nov 3, 2026, 02:26 UTC
- Message-ID
- <xmqqh5hyejke.fsf@gitster.g>
- In-Reply-To
- <DML7B6VVFDH0.3RKFXWKOH0X2L@lfurio.us>
"Matt Hunter" <m@lfurio.us> writes:
> So, I think this <A>...<B> form would yield the expected output if you > only rewrote history in-place _on the same base commit_, but not in the > general case?
That is my conclusion and my reason why I do not rebase topic branches without a good reason. It is so handy to be able to do
$ git range-diff @{1}...after updating the current topic, instead of having to do
$ git range-diff main..@{1} main..HEADwhere 'main' may have advanced since the previous round forked from it, or the current round was rebased onto it.