LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Markus Heiser <markus.heiser@darmarit.de>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Jani Nikula <jani.nikula@linux.intel.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC 0/2] docs: Deal with some Sphinx deprecation warnings
Date: Wed, 22 May 2019 09:45:59 -0600 [thread overview]
Message-ID: <20190522094559.5ed8021e@lwn.net> (raw)
In-Reply-To: <39b12927-9bf9-a304-4108-8f471a204f89@darmarit.de>
On Wed, 22 May 2019 15:25:36 +0200
Markus Heiser <markus.heiser@darmarit.de> wrote:
> Lets use 1.7 :
>
> - no need for Use_SSI wrapper
> - new log should work with 1.7 [1] --> no need for kernellog.py and
> additional imports, instead include on top of python modules ::
>
> from sphinx.util import logging
> logger = logging.getLogger('kerneldoc')
I think we're going to have to drag things forward at some point in the
not-too-distant future, but I think I'd rather not do that quite yet. The
cost of supporting older sphinx for a few releases while we warn people is
not all that high. So I think we should:
- Put in (a future version of) my hacks for now, plus whatever else might
be needed to make 2.0 work right.
- Fix the fallout with regard to out-of-toctree .rst files so that we can
actually build again with current sphinx.
- Update Documentation/sphinx/requirements.txt to ask for something a wee
bit more recent than 1.4.9.
- Add a warning when building with an older version that (say) 1.7 will
be required as of (say) 5.5.
Does this make sense?
Thanks,
jon
next prev parent reply other threads:[~2019-05-22 15:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 21:17 Jonathan Corbet
2019-05-21 21:17 ` [PATCH 1/2] doc: Cope with Sphinx logging deprecations Jonathan Corbet
2019-05-21 21:17 ` [PATCH 2/2] doc: Cope with the deprecation of AutoReporter Jonathan Corbet
2019-05-22 7:38 ` Jani Nikula
2019-05-22 7:36 ` [PATCH RFC 0/2] docs: Deal with some Sphinx deprecation warnings Jani Nikula
2019-05-22 10:19 ` Mauro Carvalho Chehab
2019-05-22 13:25 ` Markus Heiser
2019-05-22 15:45 ` Jonathan Corbet [this message]
2019-05-22 16:04 ` Mauro Carvalho Chehab
2019-05-22 16:40 ` Mauro Carvalho Chehab
2019-05-22 9:43 ` Oleksandr Natalenko
2019-05-22 9:49 ` Oleksandr Natalenko
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=20190522094559.5ed8021e@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=markus.heiser@darmarit.de \
--cc=mchehab@kernel.org \
--subject='Re: [PATCH RFC 0/2] docs: Deal with some Sphinx deprecation warnings' \
/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
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).