From: Randy Dunlap <rdunlap@infradead.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux Kernel Workflows <workflows@vger.kernel.org>
Cc: "Jonathan Corbet" <corbet@lwn.net>,
"Fox Foster" <fox@tardis.ed.ac.uk>,
"Federico Vaga" <federico.vaga@vaga.pv.it>,
"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
Subject: Re: [PATCH] Documentation: management-style: Correct "know" past participle
Date: Mon, 25 Aug 2025 23:54:22 -0700 [thread overview]
Message-ID: <67d355fc-7ee9-4203-9578-095004c4a7e6@infradead.org> (raw)
In-Reply-To: <20250826003437.7695-2-bagasdotme@gmail.com>
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@gmail.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
next prev parent reply other threads:[~2025-08-26 6:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-26 0:34 [PATCH] Documentation: management-style: Correct "know" past participle Bagas Sanjaya
2025-08-26 4:47 ` Jonathan Corbet
2025-08-26 7:40 ` Bagas Sanjaya
2025-08-26 8:25 ` Stephen Rothwell
2025-08-26 14:46 ` Konstantin Ryabitsev
2025-08-26 15:22 ` Jonathan Corbet
2025-08-26 23:54 ` Bagas Sanjaya
2025-08-26 6:54 ` Randy Dunlap [this message]
2025-08-26 7:42 ` Bagas Sanjaya
2025-08-26 11:53 ` Matthew Wilcox
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=67d355fc-7ee9-4203-9578-095004c4a7e6@infradead.org \
--to=rdunlap@infradead.org \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=federico.vaga@vaga.pv.it \
--cc=fox@tardis.ed.ac.uk \
--cc=j.neuschaefer@gmx.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).