linux-kernel - Re: [RFC PATCH v1 2/2] docs: regressions.rst: rules of thumb for handling regressions

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87sfu3woj1.fsf@meer.lwn.net>
Date:   Tue, 04 Jan 2022 07:42:26 -0700
From:   Jonathan Corbet <corbet@....net>
To:     Thorsten Leemhuis <linux@...mhuis.info>,
        Lukas Bulwahn <lukas.bulwahn@...il.com>
Cc:     "open list:DOCUMENTATION" <linux-doc@...r.kernel.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        workflows@...r.kernel.org,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Randy Dunlap <rdunlap@...radead.org>
Subject: Re: [RFC PATCH v1 2/2] docs: regressions.rst: rules of thumb for
 handling regressions

Thorsten Leemhuis <linux@...mhuis.info> writes:

> On 04.01.22 13:16, Lukas Bulwahn wrote:
>> On Mon, Jan 3, 2022 at 3:23 PM Thorsten Leemhuis <linux@...mhuis.info> 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.

>> financial support) for such further
>> documentation on the development process, please reach out to me and I
>> will see what I can do.

Financial support for documentation work?  Now there's a nice idea...:)

(back to real work now)

jon