From: Kees Cook <kees@kernel.org>
To: Runxi Yu <me@runxiyu.org>
Cc: Jonathan Corbet <corbet@lwn.net>, Sasha Levin <sashal@kernel.org>,
Randy Dunlap <rdunlap@infradead.org>,
Runxi Yu <runxiyu@umich.edu>, SeongJae Park <sj@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] README: Don't organize the README by arbitrary "roles"
Date: Wed, 13 May 2026 18:46:29 -0700 [thread overview]
Message-ID: <202605131844.085EF96F@keescook> (raw)
In-Reply-To: <20260514000954.32172-1-me@runxiyu.org>
On Thu, May 14, 2026 at 12:09:46AM +0000, Runxi Yu wrote:
> More broadly though, I'm a little skeptical in whether the README is the
> proper place to put extensive links to different subsystems/parts of the
> documentation. Sphinx has the ability to generate table of contents, and
> we could also improve the index over there, with the TOC/whatever that
> it could generate. I don't think we should be duplicating this into the
> README, but if that ship has sailed, this patch might still be useful.
I don't agree with this change at all. This modern layout of the README
was discussed at length. The "role" sections are very intentional.
-Kees
--
Kees Cook
next prev parent reply other threads:[~2026-05-14 1:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 0:09 [PATCH v2] README: Don't organize the README by arbitrary "roles" Runxi Yu
2026-05-14 1:46 ` Kees Cook [this message]
2026-05-14 1:50 ` Runxi Yu
2026-05-14 1:53 ` Kees Cook
2026-05-15 13:52 ` 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=202605131844.085EF96F@keescook \
--to=kees@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=me@runxiyu.org \
--cc=rdunlap@infradead.org \
--cc=runxiyu@umich.edu \
--cc=sashal@kernel.org \
--cc=sj@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