qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Markus Armbruster <armbru@redhat.com>,
	Michael Roth <michael.roth@amd.com>
Subject: Re: [PATCH 0/2] docs/python: bump minimum Sphinx version
Date: Tue, 2 Jul 2024 16:01:24 -0400	[thread overview]
Message-ID: <CAFn=p-Y1r3SfoA=T9rPMnTzk2ZiF28R8GUCGmLdEdhFnSDzarA@mail.gmail.com> (raw)
In-Reply-To: <20240702195903.204007-1-jsnow@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1374 bytes --]

On Tue, Jul 2, 2024 at 3:59 PM John Snow <jsnow@redhat.com> wrote:

> With recent deprecations, we can advance our minimum sphinx version
> safely. This is heavily motivated by new qapidoc work which is much
> easier to maintain cross-version compatibility for - see difficulties in
> our dbus documentation which only works on sphinx >= 4.
>
> We can only guarantee >= 3.4.3 now, but that's still vastly easier than
> maintaining compatibility all the way back to 1.x.
>
> GitLab: https://gitlab.com/jsnow/qemu/-/pipelines/1357902509
>
> (failures appear to be unrelated to the series.)
>
> John Snow (2):
>   Python: bump minimum sphinx version to 3.4.3
>   docs: remove Sphinx 1.x compatibility code
>
>  docs/conf.py             |  7 +++----
>  docs/sphinx/hxtool.py    | 21 ++++-----------------
>  docs/sphinx/kerneldoc.py | 38 ++++++++++++--------------------------
>  docs/sphinx/kernellog.py | 28 ----------------------------
>  docs/sphinx/qapidoc.py   | 29 +++--------------------------
>  pythondeps.toml          |  2 +-
>  6 files changed, 23 insertions(+), 102 deletions(-)
>  delete mode 100644 docs/sphinx/kernellog.py
>
> --
> 2.45.0
>

Bleurgh. I meant to shuffle some of the changes in patch 1 into patch 2,
I'll fix that on re-spin. If you want to review it anyway, just presume
I'll fix that next go-around.

--js

[-- Attachment #2: Type: text/html, Size: 1924 bytes --]

  parent reply	other threads:[~2024-07-02 20:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-02 19:59 [PATCH 0/2] docs/python: bump minimum Sphinx version John Snow
2024-07-02 19:59 ` [PATCH 1/2] Python: bump minimum sphinx version to 3.4.3 John Snow
2024-07-03  8:00   ` Paolo Bonzini
2024-07-03 12:06     ` John Snow
2024-07-03 12:12       ` Paolo Bonzini
2024-07-03 15:24         ` John Snow
2024-07-03 16:07           ` Paolo Bonzini
2024-07-02 19:59 ` [PATCH 2/2] docs: remove Sphinx 1.x compatibility code John Snow
2024-07-02 20:01 ` John Snow [this message]
2024-07-03  5:13   ` [PATCH 0/2] docs/python: bump minimum Sphinx version Markus Armbruster

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='CAFn=p-Y1r3SfoA=T9rPMnTzk2ZiF28R8GUCGmLdEdhFnSDzarA@mail.gmail.com' \
    --to=jsnow@redhat.com \
    --cc=armbru@redhat.com \
    --cc=michael.roth@amd.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.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).