From: Junio C Hamano <gitster@pobox.com>
To: "Matt Hunter" <m@lfurio.us>
Cc: "Ben Knoble" <ben.knoble@gmail.com>,
"Harald Nordgren" <haraldnordgren@gmail.com>,
<git@vger.kernel.org>,
"Harald Nordgren via GitGitGadget" <gitgitgadget@gmail.com>
Subject: Re: [PATCH v3] range-diff: add --matched-only to skip one-sided commits
Date: Mon, 02 Nov 2026 18:26:57 -0800 [thread overview]
Message-ID: <xmqqh5hyejke.fsf@gitster.g> (raw)
In-Reply-To: <DML7B6VVFDH0.3RKFXWKOH0X2L@lfurio.us> (Matt Hunter's message of "Mon, 02 Nov 2026 20:56:59 -0500")
"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..HEAD
where 'main' may have advanced since the previous round forked from
it, or the current round was rebased onto it.
next prev parent reply other threads:[~2026-11-03 2:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 16:41 [PATCH] range-diff: add --matched-only to skip one-sided commits Harald Nordgren via GitGitGadget
2026-09-11 17:19 ` Junio C Hamano
2026-09-11 18:48 ` Harald Nordgren
2026-09-11 18:52 ` Junio C Hamano
2026-09-11 19:01 ` Harald Nordgren
2026-09-11 19:05 ` Junio C Hamano
2026-09-11 20:55 ` [PATCH v2] " Harald Nordgren via GitGitGadget
2026-09-14 16:33 ` Junio C Hamano
2026-09-15 7:51 ` [PATCH v3] " Harald Nordgren via GitGitGadget
2026-11-02 9:21 ` Junio C Hamano
2026-11-02 10:05 ` Harald Nordgren
2026-11-02 16:47 ` Ben Knoble
2026-11-02 21:03 ` Harald Nordgren
2026-11-02 21:15 ` Harald Nordgren
2026-11-03 0:01 ` Matt Hunter
2026-11-03 0:16 ` Junio C Hamano
2026-11-03 1:10 ` Ben Knoble
2026-11-03 1:56 ` Matt Hunter
2026-11-03 2:26 ` Junio C Hamano [this message]
2026-11-02 22:01 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqh5hyejke.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=ben.knoble@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=haraldnordgren@gmail.com \
--cc=m@lfurio.us \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.