From: Jonathan Corbet <corbet@lwn.net>
To: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Jani Nikula <jani.nikula@linux.intel.com>
Subject: Re: [PATCH v2 0/6] docs: Improvements to our HTML output
Date: Tue, 11 Oct 2022 15:40:40 -0600 [thread overview]
Message-ID: <875ygqninb.fsf@meer.lwn.net> (raw)
In-Reply-To: <20221011210450.6eb13ec6@sal.lan>
Mauro Carvalho Chehab <mchehab@kernel.org> writes:
> No objections from my side. Surely more things could be tweaked. In
> particular, I didn't like having two ToCs at the index (a complete one
> and a second one pointing to where we are at the docs), but that's a lot
> better than before, so, I'm OK with that.
Oops...that was actually a leftover from my initial attempts to improve
the information there. That's not what the patches create...I've
updated the rendered docs to reflect the actual output.
Sorry for the confusion,
jon
next prev parent reply other threads:[~2022-10-11 21:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 19:00 [PATCH v2 0/6] docs: Improvements to our HTML output Jonathan Corbet
2022-10-11 19:00 ` [PATCH v2 1/6] docs: Switch the default HTML theme to alabaster Jonathan Corbet
2022-10-11 19:00 ` [PATCH v2 2/6] docs: tweak some Alabaster style parameters Jonathan Corbet
2022-10-11 19:00 ` [PATCH v2 3/6] docs: update sphinx.rst to reflect the default theme change Jonathan Corbet
2022-10-11 19:00 ` [PATCH v2 4/6] docs: sphinx-pre-install: don't require the RTD theme Jonathan Corbet
2022-10-11 19:00 ` [PATCH v2 5/6] docs: improve the HTML formatting of kerneldoc comments Jonathan Corbet
2022-10-11 19:00 ` [PATCH v2 6/6] docs: decruft Documentation/conf.py Jonathan Corbet
2022-10-11 20:04 ` [PATCH v2 0/6] docs: Improvements to our HTML output Mauro Carvalho Chehab
2022-10-11 21:40 ` Jonathan Corbet [this message]
2022-10-12 2:10 ` Bagas Sanjaya
2022-10-12 2:25 ` Randy Dunlap
2022-10-12 4:20 ` Bagas Sanjaya
2022-10-12 12:38 ` Jonathan Corbet
2022-10-13 14:21 ` Akira Yokosawa
2022-10-13 17:23 ` Jonathan Corbet
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=875ygqninb.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=jani.nikula@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@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;
as well as URLs for NNTP newsgroup(s).