From: Thorsten Leemhuis <email@example.com>
To: Randy Dunlap <firstname.lastname@example.org>,
Jonathan Corbet <email@example.com>,
Lukas Bulwahn <firstname.lastname@example.org>
Cc: "open list:DOCUMENTATION" <email@example.com>,
Linus Torvalds <firstname.lastname@example.org>,
Greg Kroah-Hartman <email@example.com>,
Linux Kernel Mailing List <firstname.lastname@example.org>
Subject: Re: [RFC PATCH v1 2/2] docs: regressions.rst: rules of thumb for handling regressions
Date: Tue, 4 Jan 2022 19:02:03 +0100 [thread overview]
Message-ID: <email@example.com> (raw)
On 04.01.22 16:09, Randy Dunlap wrote:
> On 1/4/22 06:42, Jonathan Corbet wrote:
>> Thorsten Leemhuis <firstname.lastname@example.org> writes:
>>> On 04.01.22 13:16, Lukas Bulwahn wrote:
>>>> On Mon, Jan 3, 2022 at 3:23 PM Thorsten Leemhuis <email@example.com> wrote:
>>>>> +Try to fix regressions quickly once the culprit got identified. Fixes for most
>>>> s/got/gets/ --- at least, that is what the gmail grammar spelling suggests :)
>>> Hmm, LanguageTool didn't complain. Not totally sure, maybe both
>>> approaches are okay. But the variant suggested by the gmail checker
>>> might be the better one.
>> So we're deeply into nit territory, but "gets" would be the correct
>> tense there. Even better, though, is to avoid using "to get" in this
>> way at all. I'm informed that "to get" is one of the hardest verbs for
>> non-native speakers, well, to get, so I try to avoid it in my own
>> writing. "once the culprit is identified" or "has been identified"
>> would both be good here.
> Agreed. Any uses of the verb get/got are best avoided.
Ahh, good to known, thx to both of you. I guess my English teachers
tried to put that into my head like 30 years ago, but I assume the lossy
compression algorithm in there threw it away...
Went through the document and removed all get/got, was not that hard
most of the time.
next prev parent reply other threads:[~2022-01-04 18:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 9:50 [RFC PATCH v1 0/2] docs: add a document dedicated to regressions Thorsten Leemhuis
2022-01-03 9:50 ` [RFC PATCH v1 1/2] docs: add a document about regression handling Thorsten Leemhuis
2022-01-03 17:07 ` Jakub Kicinski
2022-01-03 17:20 ` Thorsten Leemhuis
2022-01-03 17:55 ` Jakub Kicinski
2022-01-04 14:17 ` Lukas Bulwahn
2022-01-04 17:57 ` Thorsten Leemhuis
2022-01-05 8:45 ` Lukas Bulwahn
2022-01-03 9:50 ` [RFC PATCH v1 2/2] docs: regressions.rst: rules of thumb for handling regressions Thorsten Leemhuis
2022-01-04 12:16 ` Lukas Bulwahn
2022-01-04 13:29 ` Thorsten Leemhuis
2022-01-04 14:42 ` Jonathan Corbet
2022-01-04 15:09 ` Randy Dunlap
2022-01-04 18:02 ` Thorsten Leemhuis [this message]
2022-01-03 14:01 ` [RFC PATCH v1 0/2] docs: add a document dedicated to regressions Greg Kroah-Hartman
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.