git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v2 1/2] Documentation/config: fix typos

From
KHKristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Date
Sep 23, 2024, 18:43 UTC
Message-ID
<85ed3ec6-fa4e-4ab8-872f-6bd500b2bb66@app.fastmail.com>
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
Previous: Andrew KreimerNext: Eric Sunshine
Message 6 of 9 in “Documentation/config: fix typos”
  1. 1/2 Documentation/config: fix typosAndrew Kreimer, Sep 23, 2024
  2. 2/2 Documentation: fix typosAndrew Kreimer, Sep 23, 2024
  3. Eric SunshineSep 23, 2024
  4. Eric SunshineSep 23, 2024
  5. Andrew KreimerSep 23, 2024
  6. Kristoffer HaugsbakkSep 23, 2024
  7. Eric SunshineSep 23, 2024
  8. Kristoffer HaugsbakkSep 23, 2024
  9. Kristoffer HaugsbakkNov 25, 2024

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.