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

Re: How mantainers check Git diffs and patches?

From
KHKristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Date
Oct 1, 2025, 08:15 UTC
Message-ID
<ba6b9a5e-72b5-4d66-a484-37140438702a@app.fastmail.com>
In-Reply-To
<aNygY8Cm7LEaBzV6@localhost>
On Wed, Oct 1, 2025, at 05:30, Henrique Soares wrote:
Show 11 quoted lines
> This is a simple question I have related to the PR diff review process.
>
> How Git maintainers use to check diffs and review the code? I mean,
> sometimes I see that there are some large PATCHES that is hard or
> probably impossible to review only using e-mail client.
>
> Do you use some syntax highlight in client e-mail; any pipeline that
> automatically download e-mails and apply to a local branch; or for each
> PR you save the e-mail file then "git apply" to review / test the diff?
>
> This isn't a technical question, I'm just curious about how you do it.
Here is a relevant message (2016).
https://lore.kernel.org/git/20160809113703.57irthzzpg6j3dmv@sigill.intra.peff.net/
Previous: Henrique SoaresNext: Jeff King
Message 2 of 9 in “How mantainers check Git diffs and patches?”
  1. Henrique SoaresOct 1, 2025
  2. Kristoffer HaugsbakkOct 1, 2025
  3. Jeff KingOct 1, 2025
  4. Henrique SoaresOct 2, 2025
  5. Konstantin RyabitsevOct 1, 2025
  6. Henrique SoaresOct 2, 2025
  7. Junio C HamanoOct 1, 2025
  8. Henrique SoaresOct 2, 2025
  9. Junio C HamanoOct 2, 2025

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.