From: Jonathan Corbet <corbet@lwn.net>
To: Thorsten Leemhuis <linux@leemhuis.info>, linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Kees Cook <keescook@chromium.org>,
Jani Nikula <jani.nikula@linux.intel.com>,
Joe Perches <joe@perches.com>, David Vernet <void@manifault.com>
Subject: Re: [PATCH v3 7/7] docs: add a man-pages link to the front page
Date: Wed, 28 Sep 2022 15:00:37 -0600 [thread overview]
Message-ID: <8735cbkydm.fsf@meer.lwn.net> (raw)
In-Reply-To: <ff413763-6cac-576f-7671-2f883bb56c51@leemhuis.info>
Thorsten Leemhuis <linux@leemhuis.info> writes:
> On 27.09.22 18:05, Jonathan Corbet wrote:
>> Readers looking for user-oriented information may benefit from it.
>>
>> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
>> ---
>> Documentation/index.rst | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/Documentation/index.rst b/Documentation/index.rst
>> index 5a700548ae82..85eab6e990ab 100644
>> --- a/Documentation/index.rst
>> +++ b/Documentation/index.rst
>> @@ -76,6 +76,8 @@ developers seeking information on the kernel's user-space APIs.
>> User-space tools <tools/index>
>> userspace-api/index
>>
>> +See also: the `Linux man pages <https://www.kernel.org/doc/man-pages/>`_,
>> +which are kept separately from the kernel's own documentation.
>
> People following that link might be inclined to click on the section 1
> and then find a lot of stuff that has nothing or not much to do with the
> kernel and then might feel lost. So how about a text like this instead:
>
> ```
> See also the `Linux man pages <https://www.kernel.org/doc/man-pages/>`_,
> as that where some of the kernel's documentation is kept. Among it are
> for example descriptions of Linux' `system calls
> <https://man7.org/linux/man-pages/dir_section_2.html>`_ and `devices
> <https://man7.org/linux/man-pages/dir_section_4.html>`_; the sections
> `files <https://man7.org/linux/man-pages/dir_section_5.html>`_ and
> `overviews, conventions, and miscellaneous
> <https://man7.org/linux/man-pages/dir_section_7.html>`_ also contain
> many documents dedicated to aspects of the kernel.
> ```
Honestly, if the landing page for the man pages is not sufficiently
clear to guide readers toward their goal, then I think the fix needs to
be applied there. Reproducing parts of it on the kernel front page
seems like the wrong solution, somehow...
Thanks,
jon
next prev parent reply other threads:[~2022-09-28 21:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 16:05 [PATCH v3 0/7] Rewrite the top-level index.rst Jonathan Corbet
2022-09-27 16:05 ` [PATCH v3 1/7] docs: promote the title of process/index.rst Jonathan Corbet
2022-09-27 16:05 ` [PATCH v3 2/7] docs: Rewrite the front page Jonathan Corbet
2022-09-28 3:32 ` Bagas Sanjaya
2022-09-27 16:05 ` [PATCH v3 3/7] docs: reconfigure the HTML left column Jonathan Corbet
2022-09-27 16:05 ` [PATCH v3 4/7] docs: remove some index.rst cruft Jonathan Corbet
2022-09-27 16:05 ` [PATCH v3 5/7] docs: move asm-annotations.rst into core-api Jonathan Corbet
2022-09-27 16:05 ` [PATCH v3 6/7] docs: put atomic*.txt and memory-barriers.txt into the core-api book Jonathan Corbet
2022-09-27 19:26 ` David Vernet
2022-09-27 16:05 ` [PATCH v3 7/7] docs: add a man-pages link to the front page Jonathan Corbet
2022-09-27 19:28 ` David Vernet
2022-09-28 6:21 ` Thorsten Leemhuis
2022-09-28 15:03 ` Randy Dunlap
2022-09-28 21:00 ` Jonathan Corbet [this message]
2022-09-27 16:21 ` [PATCH v3 0/7] Rewrite the top-level index.rst Joe Perches
2022-09-27 20:59 ` Randy Dunlap
2022-09-29 15:34 ` Jonathan Corbet
2022-09-29 15:59 ` Kees Cook
2022-09-29 17:31 ` Jonathan Corbet
2022-09-29 19:28 ` Jonathan Corbet
2022-09-29 17:47 ` Miguel Ojeda
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=8735cbkydm.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=jani.nikula@linux.intel.com \
--cc=joe@perches.com \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=void@manifault.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).