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

Re: Draft of Git Rev News edition 133

From
KHKristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Date
Mar 30, 2026, 17:20 UTC
Message-ID
<b5c66f24-7bfd-464c-afb3-745bf3f49381@app.fastmail.com>
In-Reply-To
<CAP8UFD2HhBq3MPD30jb0XJw0hciTyB=BNjcH9s9hjBoocFqQjg@mail.gmail.com>
Git Rev News Draft wrote:
Show 12 quoted lines
> On February 6, 2026, Matthias Beyer forwarded to the Git mailing list a
> surprising warning that had just circulated on Mastodon:
>
> [...]
>
> The thread also served as a useful reminder that this problem is not
> limited to email workflows: any project that generates patches from
> Git commits using `git-format-patch` and applies them with `patch(1)`
> or `git-am` is exposed to it. The practical advice for authors is
> simple: if you include diffs in commit messages for illustrative
> purposes, make sure to indent them consistently, and be aware that
> even that does not protect you from `patch(1)`.
Very nice treatment of this topic.
This is useful since there were so many subthreads.
-- 
Kristoffer Haugsbakk
Previous: Christian Couder
Message 2 of 2 in “Draft of Git Rev News edition 133”
  1. Christian CouderMar 30, 2026
  2. Kristoffer HaugsbakkMar 30, 2026

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.