linux-kernel - Re: [PATCH] Documentation: management-style: Correct "know" past participle

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: <67d355fc-7ee9-4203-9578-095004c4a7e6@infradead.org>
Date: Mon, 25 Aug 2025 23:54:22 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: Bagas Sanjaya <bagasdotme@...il.com>,
 Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
 Linux Documentation <linux-doc@...r.kernel.org>,
 Linux Kernel Workflows <workflows@...r.kernel.org>
Cc: Jonathan Corbet <corbet@....net>, Fox Foster <fox@...dis.ed.ac.uk>,
 Federico Vaga <federico.vaga@...a.pv.it>,
 Jonathan Neuschäfer <j.neuschaefer@....net>
Subject: Re: [PATCH] Documentation: management-style: Correct "know" past
 participle



On 8/25/25 5:34 PM, Bagas Sanjaya wrote:
> Management style docs writes on people under a manager, where they know
> the details better than the manager himself, in past perfect tense. Yet,
> "know" is in infinitive form instead.
> 
> Correct the verb form.
> 

Hi Bagas,

I don't know about the patch description/argument/justification,
but the wording makes no sense to me...

> Signed-off-by: Bagas Sanjaya <bagasdotme@...il.com>
> ---
>  Documentation/process/management-style.rst | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/process/management-style.rst b/Documentation/process/management-style.rst
> index dfbc69bf49d435..1381b253b19ef4 100644
> --- a/Documentation/process/management-style.rst
> +++ b/Documentation/process/management-style.rst
> @@ -42,7 +42,7 @@ actually true.
>  The name of the game is to **avoid** having to make a decision.  In
>  particular, if somebody tells you "choose (a) or (b), we really need you
>  to decide on this", you're in trouble as a manager.  The people you
> -manage had better know the details better than you, so if they come to
> +manage had better known the details than you, so if they come to
>  you for a technical decision, you're screwed.  You're clearly not
>  competent to make that decision for them.
>  
> @@ -115,7 +115,7 @@ sure as hell shouldn't encourage them by promising them that what they
>  work on will be included.  Make them at least think twice before they
>  embark on a big endeavor.
>  
> -Remember: they'd better know more about the details than you do, and
> +Remember: they'd better known more about the details than you do, and
>  they usually already think they have the answer to everything.  The best
>  thing you can do as a manager is not to instill confidence, but rather a
>  healthy dose of critical thinking on what they do.
> 
> base-commit: ee9a6691935490dc39605882b41b9452844d5e4e

-- 
~Randy