From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
To: "Christian Couder" <christian.couder@gmail.com>,
git <git@vger.kernel.org>
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Jakub Narebski" <jnareb@gmail.com>,
"Markus Jansen" <mja@jansen-preisler.de>,
"Kaartic Sivaraam" <kaartic.sivaraam@gmail.com>,
"Štěpán Němec" <stepnem@gmail.com>,
"Taylor Blau" <me@ttaylorr.com>,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"Jeff King" <peff@peff.net>,
"Olamide Caleb Bello" <belkid98@gmail.com>,
"Matthias Beyer" <mail@beyermatthias.de>,
"Jacob Keller" <jacob.keller@gmail.com>,
"Florian Weimer" <fweimer@redhat.com>,
"Jakob Haufe" <sur5r@sur5r.net>,
"Christoph Anton Mitterer" <calestyo@scientia.org>,
"Phillip Wood" <phillip.wood123@gmail.com>,
"Patrick Steinhardt" <ps@pks.im>
Subject: Re: Draft of Git Rev News edition 133
Date: Mon, 30 Mar 2026 19:20:57 +0200 [thread overview]
Message-ID: <b5c66f24-7bfd-464c-afb3-745bf3f49381@app.fastmail.com> (raw)
In-Reply-To: <CAP8UFD2HhBq3MPD30jb0XJw0hciTyB=BNjcH9s9hjBoocFqQjg@mail.gmail.com>
Git Rev News Draft wrote:
> 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
prev parent reply other threads:[~2026-03-30 17:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 10:31 Draft of Git Rev News edition 133 Christian Couder
2026-03-30 17:20 ` Kristoffer Haugsbakk [this message]
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=b5c66f24-7bfd-464c-afb3-745bf3f49381@app.fastmail.com \
--to=kristofferhaugsbakk@fastmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=belkid98@gmail.com \
--cc=calestyo@scientia.org \
--cc=christian.couder@gmail.com \
--cc=fweimer@redhat.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jacob.keller@gmail.com \
--cc=jnareb@gmail.com \
--cc=kaartic.sivaraam@gmail.com \
--cc=mail@beyermatthias.de \
--cc=me@ttaylorr.com \
--cc=mja@jansen-preisler.de \
--cc=peff@peff.net \
--cc=phillip.wood123@gmail.com \
--cc=ps@pks.im \
--cc=stepnem@gmail.com \
--cc=sur5r@sur5r.net \
/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