From: Jonathan Corbet <corbet@lwn.net>
To: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>, linux-doc@vger.kernel.org
Cc: linux-arch@vger.kernel.org,
"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org
Subject: Re: [RFC PATCH] docs: Group arch-specific documentation under "CPU Architectures"
Date: Mon, 15 Mar 2021 13:52:14 -0600 [thread overview]
Message-ID: <87k0q819g1.fsf@meer.lwn.net> (raw)
In-Reply-To: <20210312152804.2110703-1-j.neuschaefer@gmx.net>
Jonathan Neuschäfer <j.neuschaefer@gmx.net> writes:
> To declutter the top-level table of contents (the side bar), this
> patch reduces the architecture-specfic documentation to one top-level
> item, "CPU Architectures".
>
> Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net>
> ---
>
> As a side effect, the TOC in index.html effectively gets one level of
> detail less. This could be fixed by specifying ':maxdepth: 3'.
> ---
> Documentation/arch.rst | 26 ++++++++++++++++++++++++++
> Documentation/index.rst | 20 ++------------------
> 2 files changed, 28 insertions(+), 18 deletions(-)
> create mode 100644 Documentation/arch.rst
I've badly wanted to clean up that page for a long time; this is a step
in that direction, so I'm happy to see it. Applied, thanks.
And no, we need *less* detail on the front page, not more, so no need to
bring all that back.
Thanks,
jon
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2021-03-15 19:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 15:28 [RFC PATCH] docs: Group arch-specific documentation under "CPU Architectures" Jonathan Neuschäfer
2021-03-15 19:52 ` 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=87k0q819g1.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=aou@eecs.berkeley.edu \
--cc=j.neuschaefer@gmx.net \
--cc=linux-arch@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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;
as well as URLs for NNTP newsgroup(s).