From: Randy Dunlap <rdunlap@infradead.org>
To: Thorsten Leemhuis <linux@leemhuis.info>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: workflows@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
regressions@lists.linux.dev,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>
Subject: Re: [PATCH v3 1/2] docs: add a document about regression handling
Date: Wed, 26 Jan 2022 09:16:43 -0800 [thread overview]
Message-ID: <4b433d55-95de-963b-7351-6db79855824b@infradead.org> (raw)
In-Reply-To: <c8d7228a-2df5-df92-6d53-c3e940274dad@leemhuis.info>
On 1/26/22 06:10, Thorsten Leemhuis wrote:
>>> +The important bits for people affected by regressions
>>> +=====================================================
>>> +
>>> +It's a regression if something running fine with one Linux kernel works worse or
>>> +not at all with a newer version. Note, the newer kernel has to be compiled using
>>> +a similar configuration -- for this and other fine print, check out below
>>> +section "What is a 'regression' and what is the 'no regressions rule'?".
>> Can we be consistent with either single or double quotes? I'd suggest
>> "double quotes" but won't make a fuss about that.
> Changed to "double quotes" everywhere in the text. But just to make sure
> I get things right: in this particular case this will result in
>
> ...section "What is a "regression" and what is the "no regressions rule"?".
>
> This looks a bit strange to me. Something in me really would like to
> quote the section's header in single quotes, but I guess grammar rules
> do not allow that, so whatever. :-D
>
I think that it was correct with the mixed quotes. Using all double
quotes here is confusing.
--
~Randy
next prev parent reply other threads:[~2022-01-26 17:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 11:44 [PATCH v3 0/2] docs: add a text about regressions to the Linux kernel's documentation Thorsten Leemhuis
2022-01-25 11:44 ` [PATCH v3 1/2] docs: add a document about regression handling Thorsten Leemhuis
2022-01-25 23:59 ` Jonathan Corbet
2022-01-26 14:10 ` Thorsten Leemhuis
2022-01-26 17:16 ` Randy Dunlap [this message]
2022-01-31 14:22 ` Thorsten Leemhuis
2022-01-26 14:28 ` Geert Uytterhoeven
2022-02-02 11:46 ` Thorsten Leemhuis
2022-01-25 11:44 ` [PATCH v3 2/2] docs: regressions.rst: rules of thumb for handling regressions 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=4b433d55-95de-963b-7351-6db79855824b@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=lukas.bulwahn@gmail.com \
--cc=regressions@lists.linux.dev \
--cc=torvalds@linux-foundation.org \
--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