From: Jonathan Corbet <corbet@lwn.net>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: linux-kernel@vger.kernel.org, Akira Yokosawa <akiyks@gmail.com>,
Sai Vishnu M <saivishnu725@gmail.com>
Subject: Re: [PATCH 0/3] Translate sphinx-pre-install to Python
Date: Fri, 27 Jun 2025 10:36:13 -0600 [thread overview]
Message-ID: <871pr5gn0i.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250627171233.66c825ca@sal.lan>
Mauro Carvalho Chehab <mchehab+huawei@kernel.org> writes:
> Em Thu, 26 Jun 2025 10:06:28 +0200
> Mauro Carvalho Chehab <mchehab+huawei@kernel.org> escreveu:
>
>> As part of my efforts to make the doc build system more modern, it
>> follows a patch series converting sphinx-pre-install to python.
>>
>> The first patch contains a small fix to the Perl version. It is
>> interesting to have, as otherwise regression tests fail.
>>
>> The conversion itself was not hard. Most of the time I spent writing
>> scripts to test it.
>
> Hi Jon,
>
> Please see this as a RFC. There is a trivial bug here when sphinx-build
> is found (m1 and m2 variables were renamed to match). Easy to fix,
> but I'm doing other cleanups, and I'm planning to improve the regression
> test coverage.
>
> I'll be sending you a new version next week.
OK, great, thanks for the heads-up.
jon
prev parent reply other threads:[~2025-06-27 16:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 8:06 [PATCH 0/3] Translate sphinx-pre-install to Python Mauro Carvalho Chehab
2025-06-26 8:06 ` [PATCH 1/3] scripts: sphinx-pre-install: fix version check for Fedora Mauro Carvalho Chehab
2025-06-26 8:06 ` [PATCH 2/3] scripts: sphinx-pre-install: Convert script to Python Mauro Carvalho Chehab
2025-06-26 8:06 ` [PATCH 3/3] scripts: sphinx-pre-install: replace it by a Python version Mauro Carvalho Chehab
2025-06-27 15:12 ` [PATCH 0/3] Translate sphinx-pre-install to Python Mauro Carvalho Chehab
2025-06-27 16:36 ` 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=871pr5gn0i.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=akiyks@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=saivishnu725@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.