From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail•com>
To: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail•com>,
git@vger•kernel.org
Subject: Re: [PATCH] doc: patch-id: fix accidental literal blocks
Date: Sun, 28 Sep 2025 17:45:54 +0200 [thread overview]
Message-ID: <a87b3e69-20a1-46bd-8d22-ed78145cc59c@app.fastmail.com> (raw)
In-Reply-To: <0520e8f9caf.1759067095.git.code@khaugsbakk.name>
On Sun, Sep 28, 2025:
> continuation (+) for the elements following the first paragraph if you
> want to be guaranteed a predictable output
Missing period.
next prev parent reply other threads:[~2025-09-28 15:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-28 14:03 [PATCH] doc: patch-id: fix accidental literal blocks kristofferhaugsbakk
2025-09-28 15:45 ` Kristoffer Haugsbakk [this message]
2025-09-28 16:01 ` Junio C Hamano
2025-09-28 19:25 ` Kristoffer Haugsbakk
2025-09-28 19:37 ` Junio C Hamano
2025-09-29 20:47 ` [PATCH v2] " kristofferhaugsbakk
2025-09-29 22:18 ` Junio C Hamano
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=a87b3e69-20a1-46bd-8d22-ed78145cc59c@app.fastmail.com \
--to=kristofferhaugsbakk@fastmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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