From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: virtio-comment@lists.linux.dev
Subject: Re: [PATCH v2 06/10] specvars.tex: properly wrap arguments to \urldef
Date: Fri, 10 Oct 2025 14:49:57 +0100 [thread overview]
Message-ID: <875xcmx3wa.fsf@draig.linaro.org> (raw)
In-Reply-To: <20251010075318-mutt-send-email-mst@kernel.org> (Michael S. Tsirkin's message of "Fri, 10 Oct 2025 07:53:43 -0400")
"Michael S. Tsirkin" <mst@redhat.com> writes:
> On Fri, Oct 10, 2025 at 12:20:06PM +0100, Alex Bennée wrote:
>> While the space in this case is probably harmless we should be using
>> non-ambiguous argument wrappers if don't want to drown linter output
>> with noise.
>>
>> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>> Message-ID: <20251008145916.2626143-6-alex.bennee@linaro.org>
>
>
> could you be more specfic which linter complains and how?
will do - its not the only fix though. Latex is very noisy building so
I'm sure more consequential failures are being missed. It would be a big
job to tidy it up though.
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2025-10-10 13:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-10 11:20 [PATCH v2 00/10] QoL tweaks and github action Alex Bennée
2025-10-10 11:20 ` [PATCH v2 01/10] LICENSE.md: convert html to proper MarkDown Alex Bennée
2025-10-30 7:10 ` Manos Pitsidianakis
2025-10-10 11:20 ` [PATCH v2 02/10] README.md: convert embedded " Alex Bennée
2025-10-10 11:20 ` [PATCH v2 03/10] REVISION: update to 1.4-wd01 Alex Bennée
2025-10-10 11:20 ` [PATCH v2 04/10] .gitpublish: update base to current working branch Alex Bennée
2025-10-10 11:20 ` [PATCH v2 05/10] virtio-html.tex: sort package list Alex Bennée
2025-10-10 11:20 ` [PATCH v2 06/10] specvars.tex: properly wrap arguments to \urldef Alex Bennée
2025-10-10 11:53 ` Michael S. Tsirkin
2025-10-10 13:49 ` Alex Bennée [this message]
2025-10-10 11:20 ` [PATCH v2 07/10] virtio-html.cfg: implement workaround for htlatex regression Alex Bennée
2025-10-10 11:20 ` [PATCH v2 08/10] make-setup-generated: optionally add GIT metadata Alex Bennée
2025-10-10 11:52 ` Michael S. Tsirkin
2025-10-10 13:10 ` Alex Bennée
2025-10-10 13:16 ` Michael S. Tsirkin
2025-10-10 13:48 ` Alex Bennée
2025-10-10 11:20 ` [PATCH v2 09/10] Makefile: add some simple make automations Alex Bennée
2025-10-10 11:20 ` [PATCH v2 10/10] .github: add a runner to build the latest draft Alex Bennée
2025-10-10 12:00 ` Michael S. Tsirkin
2025-10-10 13:58 ` Alex Bennée
2025-10-10 14:06 ` Michael S. Tsirkin
2025-10-10 12:06 ` [PATCH v2 00/10] QoL tweaks and github action Michael S. Tsirkin
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=875xcmx3wa.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=mst@redhat.com \
--cc=virtio-comment@lists.linux.dev \
/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