From: Kees Cook <kees@kernel.org>
To: Willy Tarreau <w@1wt.eu>
Cc: Jonathan Corbet <corbet@lwn.net>,
security@kernel.org, workflows@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH 2/2] Documentation: smooth the text flow in the security bug reporting process
Date: Thu, 14 Aug 2025 14:23:07 -0700 [thread overview]
Message-ID: <202508141423.55DECF0601@keescook> (raw)
In-Reply-To: <20250814192730.19252-2-w@1wt.eu>
On Thu, Aug 14, 2025 at 09:27:30PM +0200, Willy Tarreau wrote:
> The text was presenting the team, the the e-mail address, then some of
> the expectations, then what form of e-mail is expected. By switching
> the e-mail paragraph two paragraphs later and dropping the "Contact"
> sub-section, we can have a more natural flow that presents the team,
> then its expectation, then how to best contribute, then where to send.
>
> And more importantly, it increases the chances that reporters have read
> the prerequisites before finding the e-mail address.
>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Signed-off-by: Willy Tarreau <w@1wt.eu>
Reviewed-by: Kees Cook <kees@kernel.org>
--
Kees Cook
next prev parent reply other threads:[~2025-08-14 21:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 19:27 [PATCH 1/2] Documentation: clarify the expected collaboration with security bugs reporters Willy Tarreau
2025-08-14 19:27 ` [PATCH 2/2] Documentation: smooth the text flow in the security bug reporting process Willy Tarreau
2025-08-14 21:23 ` Kees Cook [this message]
2025-08-14 21:23 ` [PATCH 1/2] Documentation: clarify the expected collaboration with security bugs reporters Kees Cook
2025-08-16 15:07 ` Greg Kroah-Hartman
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=202508141423.55DECF0601@keescook \
--to=kees@kernel.org \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=security@kernel.org \
--cc=w@1wt.eu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.