From: Jonathan Corbet <corbet@lwn.net>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Akira Yokosawa <akiyks@gmail.com>
Cc: Masaharu Noguchi <nogunix@gmail.com>,
Chen Miao <chenmiao.ku@gmail.com>,
Bagas Sanjaya <bagasdotme@gmail.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>
Subject: Re: rst2pdf (was [PATCH v2] docs: sphinx-pre-install: warn about unsupported Docutils versions)
Date: Tue, 15 Sep 2026 08:35:11 -0600 [thread overview]
Message-ID: <87h5jqd1ls.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260915101638.76e3bf1c@foz.lan>
Mauro Carvalho Chehab <mchehab+huawei@kernel.org> writes:
> On a separate but related issue, has anyone tried to use rst2pdf
> lately (https://github.com/rst2pdf/rst2pdf)?
I have a branch sitting around that, on occasion, I dust off to see how
it works; every time, rst2pdf crashes and burns. I've long wanted to
find some time to figure out what's going on and try to fix it but
... well, we know that story by now ...
It would be *wonderful* if we could us it and short the LaTeX toolchain
out entirely.
jon
next prev parent reply other threads:[~2026-09-15 14:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 10:35 [PATCH v2] docs: sphinx-pre-install: warn about unsupported Docutils versions Masaharu Noguchi
2026-09-15 7:52 ` Akira Yokosawa
2026-09-15 7:58 ` Akira Yokosawa
2026-09-15 8:16 ` Mauro Carvalho Chehab
2026-09-15 13:53 ` Masaharu Noguchi
2026-09-15 14:35 ` Jonathan Corbet [this message]
2026-09-15 18:20 ` rst2pdf (was [PATCH v2] docs: sphinx-pre-install: warn about unsupported Docutils versions) Mauro Carvalho Chehab
2026-09-15 13:41 ` [PATCH v2] docs: sphinx-pre-install: warn about unsupported Docutils versions Masaharu Noguchi
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=87h5jqd1ls.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=akiyks@gmail.com \
--cc=bagasdotme@gmail.com \
--cc=chenmiao.ku@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=mchehab@kernel.org \
--cc=nogunix@gmail.com \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.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
all inboxes | Powered by JetHome®