From: Jonathan Corbet <corbet@lwn.net>
To: "Linux regression tracking (Thorsten Leemhuis)"
<regressions@leemhuis.info>, Karel Balej <balejk@matfyz.cz>,
regressions@lists.linux.dev, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, workflows@vger.kernel.org
Subject: Re: [PATCH 1/2] docs: *-regressions.rst: unify quoting, add missing word
Date: Wed, 10 Apr 2024 15:03:29 -0600 [thread overview]
Message-ID: <874jc9szfi.fsf@meer.lwn.net> (raw)
In-Reply-To: <3e53f18c-12aa-4bf8-b3f7-7945bbca6882@leemhuis.info>
"Linux regression tracking (Thorsten Leemhuis)"
<regressions@leemhuis.info> writes:
> On 28.03.24 20:29, Karel Balej wrote:
>> Quoting of the '"no regressions" rule' expression differs between
>> occurrences, sometimes being presented as '"no regressions rule"'. Unify
>> the quoting using the first form which seems semantically correct or is
>> at least used dominantly, albeit marginally.
>>
>> One of the occurrences is obviously missing the 'rule' part -- add it.
>>
>> Signed-off-by: Karel Balej <balejk@matfyz.cz>
>
> Thx for this:
>
> Reviewed-by: Thorsten Leemhuis <linux@leemhuis.info>
I've applied this patch; part 2, it seems, is subject to further work so
I have not applied that one.
Thanks,
jon
next prev parent reply other threads:[~2024-04-10 21:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 19:29 [PATCH 0/2] regressions documentation improvements Karel Balej
2024-03-28 19:29 ` [PATCH 1/2] docs: *-regressions.rst: unify quoting, add missing word Karel Balej
2024-04-03 14:13 ` Linux regression tracking (Thorsten Leemhuis)
2024-04-10 21:03 ` Jonathan Corbet [this message]
2024-03-28 19:29 ` [PATCH 2/2] docs: handling-regressions.rst: clarify that "Closes:" tags work too Karel Balej
2024-04-01 8:38 ` Thorsten Leemhuis
2024-04-01 15:19 ` Randy Dunlap
2024-04-02 9:27 ` Thorsten Leemhuis
2024-04-02 10:13 ` Karel Balej
2024-04-03 14:13 ` Thorsten Leemhuis
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=874jc9szfi.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=balejk@matfyz.cz \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=workflows@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).