public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Kees Cook <keescook@chromium.org>
Cc: Kees Cook <keescook@chromium.org>,
	Thorsten Leemhuis <linux@leemhuis.info>,
	Rong Tao <rtoax@foxmail.com>,
	Lukas Bulwahn <lukas.bulwahn@gmail.com>,
	Zhangfei Gao <zhangfei.gao@foxmail.com>,
	linux-doc@vger.kernel.org, linux-hardening@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Tyler Hicks <code@tyhicks.com>,
	Nick Desaulniers <ndesaulniers@google.com>,
	Jiri Kosina <jikos@kernel.org>,
	Matthieu Baerts <matthieu.baerts@tessares.net>,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Xujun Leng <lengxujun2007@126.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] docs: submitting-patches: Discuss interleaved replies
Date: Fri, 19 May 2023 09:28:31 -0600	[thread overview]
Message-ID: <87ttw8mjc0.fsf@meer.lwn.net> (raw)
In-Reply-To: <20230511184131.gonna.399-kees@kernel.org>

Kees Cook <keescook@chromium.org> writes:

> Top-posting has been strongly discouraged in Linux development, but this
> was actually not written anywhere in the common documentation about
> sending patches and replying to reviews. Add a section about trimming
> and interleaved replies.
>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: Thorsten Leemhuis <linux@leemhuis.info>
> Cc: Rong Tao <rtoax@foxmail.com>
> Cc: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> Cc: Zhangfei Gao <zhangfei.gao@foxmail.com>
> Cc: linux-doc@vger.kernel.org
> Cc: linux-hardening@vger.kernel.org
> Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Signed-off-by: Kees Cook <keescook@chromium.org>
> ---
> v2:
>  - rewrite 2.Process.rst to be postive and link to new section.
>  - fix typos and phrasing (Thorsten)
>  - add missing "::" for block quotes
>  - add Greg's Ack
> v1: https://lore.kernel.org/lkml/20230510183423.never.877-kees@kernel.org
> ---
>  Documentation/process/2.Process.rst          |  7 +++---
>  Documentation/process/submitting-patches.rst | 25 ++++++++++++++++++++
>  2 files changed, 29 insertions(+), 3 deletions(-)

Applied, thanks.

jon

      parent reply	other threads:[~2023-05-19 15:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-11 18:41 [PATCH v2] docs: submitting-patches: Discuss interleaved replies Kees Cook
2023-05-13  9:13 ` Krzysztof Kozlowski
2023-05-19 15:28 ` Jonathan Corbet [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=87ttw8mjc0.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=code@tyhicks.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jikos@kernel.org \
    --cc=keescook@chromium.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=lengxujun2007@126.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@leemhuis.info \
    --cc=lukas.bulwahn@gmail.com \
    --cc=matthieu.baerts@tessares.net \
    --cc=ndesaulniers@google.com \
    --cc=rtoax@foxmail.com \
    --cc=zhangfei.gao@foxmail.com \
    /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