From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Kees Cook <keescook@chromium.org>, Jonathan Corbet <corbet@lwn.net>
Cc: 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>,
Xujun Leng <lengxujun2007@126.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] docs: submitting-patches: Discuss interleaved replies
Date: Sat, 13 May 2023 11:13:21 +0200 [thread overview]
Message-ID: <65cf0de4-42b9-2b25-ac16-9e2ddfcfdb93@linaro.org> (raw)
In-Reply-To: <20230511184131.gonna.399-kees@kernel.org>
On 11/05/2023 20:41, Kees Cook wrote:
> 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>
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-05-13 9:13 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 [this message]
2023-05-19 15:28 ` Jonathan Corbet
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=65cf0de4-42b9-2b25-ac16-9e2ddfcfdb93@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=code@tyhicks.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=jikos@kernel.org \
--cc=keescook@chromium.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