From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Jani Nikula <jani.nikula@intel.com>
Subject: Re: [PATCH 09/11] docs: Collapse the process guide TOC
Date: Wed, 26 Oct 2016 22:26:27 -0200 [thread overview]
Message-ID: <20161026222627.4370d758@vento.lan> (raw)
In-Reply-To: <1477523979-5837-10-git-send-email-corbet@lwn.net>
Em Wed, 26 Oct 2016 17:19:37 -0600
Jonathan Corbet <corbet@lwn.net> escreveu:
> I believe this makes the page as a whole more approachable.
Makes sense.
Reviewed-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
>
> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
> ---
> Documentation/process/index.rst | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/process/index.rst b/Documentation/process/index.rst
> index 0cbc62adbbb1..0557144cef2b 100644
> --- a/Documentation/process/index.rst
> +++ b/Documentation/process/index.rst
> @@ -16,7 +16,7 @@ trouble.
> Below are the essential guides that every developer should read.
>
> .. toctree::
> - :maxdepth: 2
> + :maxdepth: 1
>
> howto
> code-of-conflict
> @@ -28,7 +28,7 @@ Below are the essential guides that every developer should read.
> Other guides to the community that are of interest to most developers are:
>
> .. toctree::
> - :maxdepth: 2
> + :maxdepth: 1
>
> changes
> submitting-drivers
> @@ -42,7 +42,7 @@ These are some overall technical guides that have been put here for now for
> lack of a better place.
>
> .. toctree::
> - :maxdepth: 2
> + :maxdepth: 1
>
> applying-patches
> adding-syscalls
Thanks,
Mauro
next prev parent reply other threads:[~2016-10-27 0:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 23:19 [PATCH 00/11] Organize and clean up the admin and process guides Jonathan Corbet
2016-10-26 23:19 ` [PATCH 01/11] docs: Tweak the top-level Sphinx page Jonathan Corbet
2016-10-27 0:12 ` Mauro Carvalho Chehab
2016-10-26 23:19 ` [PATCH 02/11] docs: retitle the kernel-documentation.rst Jonathan Corbet
2016-10-27 0:13 ` Mauro Carvalho Chehab
2016-10-26 23:19 ` [PATCH 03/11] docs: Clean up and organize the admin guide a bit Jonathan Corbet
2016-10-27 0:18 ` Mauro Carvalho Chehab
2016-10-26 23:19 ` [PATCH 04/11] docs: Get rid of the badRAM guide Jonathan Corbet
2016-10-27 0:19 ` Mauro Carvalho Chehab
2016-10-26 23:19 ` [PATCH 05/11] docs: Get rid of the "basic profiling" guide Jonathan Corbet
2016-10-27 0:20 ` Mauro Carvalho Chehab
2016-10-26 23:19 ` [PATCH 06/11] docs: Get rid of the "bug-hunting" guide Jonathan Corbet
2016-10-27 0:23 ` Mauro Carvalho Chehab
2016-10-26 23:19 ` [PATCH 07/11] docs: Apply some basic organization to the process guide Jonathan Corbet
2016-10-27 0:24 ` Mauro Carvalho Chehab
2016-10-26 23:19 ` [PATCH 08/11] docs: Tweak submitting-patches.rst formatting Jonathan Corbet
2016-10-27 0:25 ` Mauro Carvalho Chehab
2016-10-26 23:19 ` [PATCH 09/11] docs: Collapse the process guide TOC Jonathan Corbet
2016-10-27 0:26 ` Mauro Carvalho Chehab [this message]
2016-10-26 23:19 ` [PATCH 10/11] docs: add a warning to submitting-drivers.rst Jonathan Corbet
2016-10-27 0:38 ` Mauro Carvalho Chehab
2016-10-26 23:19 ` [PATCH 11/11] docs: Add a warning to applying-patches.rst Jonathan Corbet
2016-10-27 0:32 ` Mauro Carvalho Chehab
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=20161026222627.4370d758@vento.lan \
--to=mchehab@s-opensource.com \
--cc=corbet@lwn.net \
--cc=jani.nikula@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@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
Powered by JetHome