From: Willy Tarreau <w@1wt.eu>
To: Kees Cook <keescook@chromium.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
security@kernel.org, corbet@lwn.net, workflows@vger.kernel.org
Subject: Re: [PATCH 2/2] Documentation: security-bugs.rst: clarify CVE handling
Date: Mon, 3 Jul 2023 21:35:11 +0200 [thread overview]
Message-ID: <ZKMi78OUCL2N5OQB@1wt.eu> (raw)
In-Reply-To: <202307031217.95B8803@keescook>
On Mon, Jul 03, 2023 at 12:26:32PM -0700, Kees Cook wrote:
> I still think this version of the sentence is more readable:
>
> However under no circumstances will patch publication be delayed for
> CVE identifier assignment.
>
> "patch inclusion" is less clear to me that "publication", and "be
> delayed to wait for" is redundant: a delay is a wait, and "to arrive"
> is just the assignment, which is the subject of the paragraph, so better
> to keep the language for that consistent.
I agree, I find it better as well :-)
Thanks,
Willy
next prev parent reply other threads:[~2023-07-03 19:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 7:14 [PATCH 1/2] Documentation: security-bugs.rst: update preferences when dealing with the linux-distros group Greg Kroah-Hartman
2023-06-30 7:14 ` [PATCH 2/2] Documentation: security-bugs.rst: clarify CVE handling Greg Kroah-Hartman
2023-06-30 7:21 ` Greg Kroah-Hartman
2023-06-30 18:18 ` Kees Cook
2023-07-02 12:39 ` Greg Kroah-Hartman
2023-07-03 4:08 ` Willy Tarreau
2023-07-03 15:00 ` Greg Kroah-Hartman
2023-07-03 18:35 ` Kees Cook
2023-07-03 19:05 ` Greg Kroah-Hartman
2023-07-03 19:26 ` Kees Cook
2023-07-03 19:35 ` Willy Tarreau [this message]
2023-06-30 18:14 ` [PATCH 1/2] Documentation: security-bugs.rst: update preferences when dealing with the linux-distros group Kees Cook
2023-07-03 15:00 ` Greg Kroah-Hartman
2023-07-03 15:01 ` 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=ZKMi78OUCL2N5OQB@1wt.eu \
--to=w@1wt.eu \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=security@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