Draft of Git Rev News edition 133

2 messages between Mar 30, 2026 and Mar 30, 2026, from Christian Couder, Kristoffer Haugsbakk.

Plain Markdown or JSON for tools and agents.

Christian CouderMar 30, 2026, 10:31 UTC on lore

Hi everyone,

A draft of a new Git Rev News edition is available here:

  https://github.com/git/git.github.io/blob/master/rev_news/drafts/edition-133.md

Everyone is welcome to contribute in any section either by editing the above page on GitHub and sending a pull request, or by commenting on this GitHub issue:

  https://github.com/git/git.github.io/issues/833

You can also reply to this email.

In general all kinds of contributions, for example proofreading, suggestions for articles or links, help on the issues in GitHub, volunteering for being interviewed and so on, are very much appreciated.

I tried to Cc everyone who appears in this edition, but maybe I missed some people, sorry about that.

Jakub, Markus, Kaartic and I plan to publish this edition on Wednesday April 1st, 2026.

Thanks, Christian.

Kristoffer HaugsbakkMar 30, 2026, 17:20 UTC in reply to Christian Couder on lore

Re: Draft of Git Rev News edition 133

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