From: Jani Nikula <jani.nikula@linux.intel.com>
To: keyrings@vger.kernel.org
Subject: Re: [PATCH 1/2] docs: Standardise capitalisation of section headers in core.rst
Date: Mon, 21 Aug 2017 09:15:26 +0000 [thread overview]
Message-ID: <87valh5ljl.fsf@nikula.org> (raw)
In-Reply-To: <20170819152106.20432-2-anowlcalledjosh@gmail.com>
On Sat, 19 Aug 2017, Josh Holland <anowlcalledjosh@gmail.com> wrote:
> The table of contents in security/keys/core.rst had different
> capitalisation to the section headers, which broke case-sensitive
> search.
>
> Signed-off-by: Josh Holland <anowlcalledjosh@gmail.com>
> ---
> Documentation/security/keys/core.rst | 22 +++++++++++-----------
> 1 file changed, 11 insertions(+), 11 deletions(-)
>
> diff --git a/Documentation/security/keys/core.rst b/Documentation/security/keys/core.rst
> index 1648fa80b..7c39c595c 100644
> --- a/Documentation/security/keys/core.rst
> +++ b/Documentation/security/keys/core.rst
> @@ -16,17 +16,17 @@ The key service can be configured on by enabling:
>
> This document has the following sections:
>
> - - Key overview
> - - Key service overview
> - - Key access permissions
> - - SELinux support
> - - New procfs files
> - - Userspace system call interface
> - - Kernel services
> - - Notes on accessing payload contents
> - - Defining a key type
> - - Request-key callback service
> - - Garbage collection
> + - Key Overview
> + - Key Service Overview
> + - Key Access Permissions
> + - SELinux Support
> + - New ProcFS Files
> + - Userspace System Call Interface
> + - Kernel Services
> + - Notes On Accessing Payload Contents
> + - Defining a Key Type
> + - Request-Key Callback Service
> + - Garbage Collection
If you want to retain the contents in .rst for the benefit of reading
this as plain text, this is fine.
However, if you want to sphinxify things a little, you could make the
resulting html a little bit nicer with automatic links, and document
maintenance a little bit easier, by replacing the hand written contents
with:
.. contents::
:local:
The maintainer's call, obviously.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2017-08-21 9:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-19 15:21 [PATCH 1/2] docs: Standardise capitalisation of section headers in core.rst Josh Holland
2017-08-21 9:15 ` Jani Nikula [this message]
2017-08-21 12:58 ` Jonathan Corbet
2017-08-23 20:34 ` Josh Holland
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=87valh5ljl.fsf@nikula.org \
--to=jani.nikula@linux.intel.com \
--cc=keyrings@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.