[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170519081117.6da0a699@vento.lan>
Date: Fri, 19 May 2017 08:11:17 -0300
From: Mauro Carvalho Chehab <mchehab@...pensource.com>
To: Johannes Berg <johannes@...solutions.net>
Cc: Linux Doc Mailing List <linux-doc@...r.kernel.org>,
Mauro Carvalho Chehab <mchehab@...radead.org>,
linux-kernel@...r.kernel.org, Jonathan Corbet <corbet@....net>,
David Woodhouse <dwmw2@...radead.org>,
Brian Norris <computersforpeace@...il.com>,
Boris Brezillon <boris.brezillon@...e-electrons.com>,
Marek Vasut <marek.vasut@...il.com>,
Richard Weinberger <richard@....at>,
Cyrille Pitchen <cyrille.pitchen@...el.com>,
linux-mtd@...ts.infradead.org, linux-wireless@...r.kernel.org
Subject: Re: [PATCH 08/29] rfkill.txt: standardize document format
Em Fri, 19 May 2017 12:15:01 +0200
Johannes Berg <johannes@...solutions.net> escreveu:
> On Thu, 2017-05-18 at 22:25 -0300, Mauro Carvalho Chehab wrote:
> >
> > +.. CONTENTS
> >
> > + 1. Introduction
> > + 2. Implementation details
> > + 3. Kernel API
> > + 4. Userspace support
>
> Why not let this be auto-generated?
>
> .. contents::
> :depth: 1
>
> should work, no?
Yes, it should work. Actually, you would need to use :depth: 2 to
produce this output:
Contents
. rfkill - RF kill switch support
. Introduction
. Implementation details
. Kernel API
. Userspace support
I opted to keep the contents as a comment just because, in the past, some
maintainers complained about TOC removal, arguing that it makes harder
for the ones that would be reading the file in ascii.
Thanks,
Mauro
Powered by blists - more mailing lists