From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
To: "D. Ben Knoble" <ben.knoble@gmail.com>
Cc: "Junio C Hamano" <gitster@pobox.com>, "Matt Hunter" <m@lfurio.us>,
"Harald Nordgren" <haraldnordgren@gmail.com>,
git@vger.kernel.org, "Thomas Bachem" <gitgitgadget@gmail.com>
Subject: Re: [PATCH v3] range-diff: add --matched-only to skip one-sided commits
Date: Wed, 04 Nov 2026 19:08:44 +0100 [thread overview]
Message-ID: <fb9a42b6-e2df-466d-89f8-77c06f3b45d0@app.fastmail.com> (raw)
In-Reply-To: <2D59CFA3-B1A6-49E3-A930-C3057D97D507@gmail.com>
On Wed, Nov 4, 2026, at 19:00, Ben Knoble wrote:
>> Le 4 nov. 2026 à 06:27, Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com> a écrit :
>>[snip]
>>
>> I use the
>>
>> base..old base..new
>>
>> Form as well.[1] Then it indeed does not matter if you have rebased or
>> not, as far as unrelated commits are concerned. You won’t get unrelated
>> commits.
>>
>> † 1: The repetition seems a bit inevitable and annoying, but I use a
>> script for assembling all of the options to git-format-patch(1).
>
> What repetition?
>
> git range-diff base old new
>
> ;)
Oh. Right! :D
next prev parent reply other threads:[~2026-11-04 18:09 UTC|newest]
Thread overview: 23+ 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
2026-11-04 11:25 ` Kristoffer Haugsbakk
2026-11-04 18:00 ` Ben Knoble
2026-11-04 18:08 ` Kristoffer Haugsbakk [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=fb9a42b6-e2df-466d-89f8-77c06f3b45d0@app.fastmail.com \
--to=kristofferhaugsbakk@fastmail.com \
--cc=ben.knoble@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox