From: Jonathan Corbet <corbet@lwn.net>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, Borislav Petkov <bp@suse.de>,
Rob Herring <robh@kernel.org>, Frank Li <Frank.li@nxp.com>,
kernel@pengutronix.de, Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: Re: [PATCH RFC 1/2] docs: process: submitting-patches: split canonical patch format section
Date: Mon, 30 Dec 2024 11:38:58 -0700 [thread overview]
Message-ID: <87v7v110e5.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20241220-submitting-patches-imperative-v1-1-ee874c1859b3@pengutronix.de>
Ahmad Fatoum <a.fatoum@pengutronix.de> writes:
> To make it easier to reference specific parts of the patch format,
> let's add some headings for different parts.
>
> Doing that, it becomes clear that backtraces in commit message is out of
> place being after Reply-To Headers, so move it next to the commit
> message body subsubsection.
>
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> ---
> Documentation/process/submitting-patches.rst | 56 +++++++++++++++++-----------
> 1 file changed, 34 insertions(+), 22 deletions(-)
This seems like an improvement - I've applied it, thanks.
jon
next prev parent reply other threads:[~2024-12-30 18:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 9:09 [PATCH RFC 0/2] docs: process: submitting-patches: clarify imperative mood suggestion Ahmad Fatoum
2024-12-20 9:09 ` [PATCH RFC 1/2] docs: process: submitting-patches: split canonical patch format section Ahmad Fatoum
2024-12-30 18:38 ` Jonathan Corbet [this message]
2024-12-20 9:09 ` [PATCH RFC 2/2] docs: process: submitting-patches: clarify imperative mood suggestion Ahmad Fatoum
2024-12-30 18:40 ` Jonathan Corbet
2025-01-06 14:51 ` Ahmad Fatoum
2025-01-06 14:57 ` Jonathan Corbet
2025-01-06 15:02 ` Ahmad Fatoum
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=87v7v110e5.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=Frank.li@nxp.com \
--cc=a.fatoum@pengutronix.de \
--cc=bp@suse.de \
--cc=kernel@pengutronix.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=workflows@vger.kernel.org \
/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