From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
To: "Eric Sunshine" <sunshine@sunshineco.com>,
"Andrew Kreimer" <algonell@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2 1/2] Documentation/config: fix typos
Date: Mon, 23 Sep 2024 20:43:39 +0200 [thread overview]
Message-ID: <85ed3ec6-fa4e-4ab8-872f-6bd500b2bb66@app.fastmail.com> (raw)
In-Reply-To: <CAPig+cSZmKCwy_sFKPR-w+DjXeTJJec1BAM6wDXMyEMWhoAY6g@mail.gmail.com>
Hi
On Mon, Sep 23, 2024, at 19:51, Eric Sunshine wrote:
> Depending upon how dramatically the patch series changes from one
> version to the next, the range-diff may end up being unreadable
> gobbledygook, in which case you may instead want to include an
> interdiff ("git format-patch --interdiff").
What’s the benefit of interdiff in that case? Neither
git-format-patch(1) nor git-range-diff(1) seems to discuss what the
differences between these two are.
--
Kristoffer Haugsbakk
next prev parent reply other threads:[~2024-09-23 18:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-23 11:03 [PATCH v2 1/2] Documentation/config: fix typos Andrew Kreimer
2024-09-23 11:03 ` [PATCH v2 2/2] Documentation: " Andrew Kreimer
2024-09-23 17:51 ` [PATCH v2 1/2] Documentation/config: " Eric Sunshine
2024-09-23 17:59 ` Eric Sunshine
2024-09-23 20:01 ` Andrew Kreimer
2024-09-23 18:43 ` Kristoffer Haugsbakk [this message]
2024-09-23 19:05 ` Eric Sunshine
2024-09-23 19:13 ` Kristoffer Haugsbakk
2024-11-25 20:20 ` Kristoffer Haugsbakk
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=85ed3ec6-fa4e-4ab8-872f-6bd500b2bb66@app.fastmail.com \
--to=kristofferhaugsbakk@fastmail.com \
--cc=algonell@gmail.com \
--cc=git@vger.kernel.org \
--cc=sunshine@sunshineco.com \
/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;
as well as URLs for NNTP newsgroup(s).