From: Jonathan Corbet <corbet@lwn.net>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: "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>,
"Fox Foster" <fox@tardis.ed.ac.uk>,
"Federico Vaga" <federico.vaga@vaga.pv.it>,
"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
"Randy Dunlap" <rdunlap@infradead.org>
Subject: Re: [PATCH] Documentation: management-style: Correct "know" past participle
Date: Tue, 26 Aug 2025 09:22:31 -0600 [thread overview]
Message-ID: <875xeaaz0o.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250826-fearless-glossy-dinosaur-46ebbf@lemur>
Konstantin Ryabitsev <konstantin@linuxfoundation.org> writes:
> I do believe this is a clear indicator that the whole sentence needs to be
> reworded:
>
> ... if somebody tells you to "choose (a) or (b), we really need you to
> decide on this," you're in trouble as a manager. The people you manage
> most likely know the details better than you, so if they come to you for
> a technical decision, ...
>
> This change would detract from the... unique... style of this document, but
> would hopefully be less confusing to non-native speakers.
There has been talk in some circles about trying to update this
... unique ... style to more contemporary standards. Maybe it's time to
see if that can be given a bit of encouragement.
Thanks,
jon
next prev parent reply other threads:[~2025-08-26 15:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-26 0:34 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 [this message]
2025-08-26 23:54 ` Bagas Sanjaya
2025-08-26 6:54 ` Randy Dunlap
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=875xeaaz0o.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=bagasdotme@gmail.com \
--cc=federico.vaga@vaga.pv.it \
--cc=fox@tardis.ed.ac.uk \
--cc=j.neuschaefer@gmx.net \
--cc=konstantin@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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