public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Vegard Nossum <vegard.nossum@oracle.com>,
	linux-doc@vger.kernel.org,
	Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: "Jani Nikula" <jani.nikula@intel.com>,
	linux-kernel@vger.kernel.org,
	"Vegard Nossum" <vegard.nossum@oracle.com>,
	"Alex Shi" <alexs@kernel.org>, "Armin Wolf" <W_Armin@gmx.de>,
	"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
	"Fangrui Song" <maskray@google.com>,
	"Federico Vaga" <federico.vaga@vaga.pv.it>,
	gaochao <gaochao49@huawei.com>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Hans de Goede" <hdegoede@redhat.com>,
	"Hu Haowen" <src.res.211@gmail.com>,
	"Iwona Winiarska" <iwona.winiarska@intel.com>,
	"Julien Panis" <jpanis@baylibre.com>,
	"Ricardo Cañuelo" <ricardo.canuelo@collabora.com>,
	"Richard Cochran" <richardcochran@gmail.com>,
	"Rui Li" <me@lirui.org>, "SeongJae Park" <sj@kernel.org>,
	"Stephan Mueller" <smueller@chronox.de>,
	"Tomas Winkler" <tomas.winkler@intel.com>,
	"Wan Jiabing" <wanjiabing@vivo.com>,
	"Wu XiangCheng" <bobwxc@email.cn>,
	"Yanteng Si" <siyanteng@loongson.cn>
Subject: Re: [PATCH RFC 00/11] use toctree :caption: for ToC headings
Date: Fri, 17 Nov 2023 13:09:24 -0700	[thread overview]
Message-ID: <87ttpk87m3.fsf@meer.lwn.net> (raw)
In-Reply-To: <20231027081830.195056-1-vegard.nossum@oracle.com>

Vegard Nossum <vegard.nossum@oracle.com> writes:

> Hi,
>
> This patch series replaces some instances of 'class:: toc-title' with
> toctree's :caption: attribute, see the last patch in the series for
> some more rationale/explanation.
>
> There are some dependencies here: the first patch is necessary for the
> headings in following patches to be styled correctly with the alabaster
> theme (rtd_sphinx already has it), and the last patch depends on most
> of the previous patches to not use the old .toc-title class anymore.
>
> Assuming people agree with the general direction, I thought maybe the
> easiest thing would be to collect maintainer acks in this round and
> then for me to resubmit everything to the documentation tree/maintainer
> in one go.

Easiest thing seems to be for me to just apply it, so I've done that.
It would have been a bit easier if you'd worked against a recent
docs-next, but so it goes...

Thanks,

jon

      parent reply	other threads:[~2023-11-17 20:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-27  8:18 [PATCH RFC 00/11] use toctree :caption: for ToC headings Vegard Nossum
2023-10-27  8:18 ` [PATCH RFC 01/11] docs: style toctree captions as headings Vegard Nossum
2023-10-27  8:18 ` [PATCH RFC 02/11] doc: userspace-api: properly format ToC headings Vegard Nossum
2023-10-27  8:18 ` [PATCH RFC 03/11] media: admin-guide: properly format ToC heading Vegard Nossum
2023-10-27  8:18 ` [PATCH RFC 04/11] crypto: doc: properly format ToC headings Vegard Nossum
2023-10-27  8:18 ` [PATCH RFC 05/11] Documentation: dev-tools: properly format ToC headingss Vegard Nossum
2023-10-27  8:18 ` [PATCH RFC 06/11] docs: driver-api: properly format ToC headings Vegard Nossum
2023-10-27  8:18 ` [PATCH RFC 07/11] input: docs: " Vegard Nossum
2023-10-27  8:18 ` [PATCH RFC 08/11] doc: misc-device: properly format ToC heading Vegard Nossum
2023-10-27  8:18 ` [PATCH RFC 09/11] media: doc: properly format ToC headings Vegard Nossum
2023-10-27  8:18 ` [PATCH RFC 10/11] docs: use toctree :caption: and move introduction Vegard Nossum
2023-10-27  8:18 ` [PATCH RFC 11/11] docs: remove .toc-title class Vegard Nossum
2023-10-27  8:32 ` [PATCH RFC 00/11] use toctree :caption: for ToC headings Jani Nikula
2023-11-17 20:09 ` 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=87ttpk87m3.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=W_Armin@gmx.de \
    --cc=alexs@kernel.org \
    --cc=bobwxc@email.cn \
    --cc=dmitry.torokhov@gmail.com \
    --cc=federico.vaga@vaga.pv.it \
    --cc=gaochao49@huawei.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hdegoede@redhat.com \
    --cc=iwona.winiarska@intel.com \
    --cc=jani.nikula@intel.com \
    --cc=jpanis@baylibre.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maskray@google.com \
    --cc=mchehab@kernel.org \
    --cc=me@lirui.org \
    --cc=ricardo.canuelo@collabora.com \
    --cc=richardcochran@gmail.com \
    --cc=siyanteng@loongson.cn \
    --cc=sj@kernel.org \
    --cc=smueller@chronox.de \
    --cc=src.res.211@gmail.com \
    --cc=tomas.winkler@intel.com \
    --cc=vegard.nossum@oracle.com \
    --cc=wanjiabing@vivo.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