From: Jonathan Corbet <corbet@lwn.net>
To: Bagas Sanjaya <bagasdotme@gmail.com>, linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Jani Nikula <jani.nikula@linux.intel.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Subject: Re: [PATCH v2 0/6] docs: Improvements to our HTML output
Date: Wed, 12 Oct 2022 06:38:51 -0600 [thread overview]
Message-ID: <87h709md2c.fsf@meer.lwn.net> (raw)
In-Reply-To: <3c65451e-c9bf-55ea-02af-f375346c955a@gmail.com>
Bagas Sanjaya <bagasdotme@gmail.com> writes:
> Hmm, I can't cleanly apply this patch series on top of either Linus's tree
> or linux-next due to conflicts on [1/6]. On what commit this series is based
> on?
docs-next, which is still running off the pre-6.0 base until after the
merge window closes.
If I need to post another round before merging I'll drag everything
forward to a more current base.
Thanks,
jon
next prev parent reply other threads:[~2022-10-12 12:38 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
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 [this message]
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=87h709md2c.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=bagasdotme@gmail.com \
--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).