From: Randy Dunlap <rdunlap@infradead.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Jonathan Corbet <corbet@lwn.net>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux Documentation" <linux-doc@vger.kernel.org>,
"Linux Kernel Workflows" <workflows@vger.kernel.org>,
"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
"Fox Foster" <fox@tardis.ed.ac.uk>,
"Federico Vaga" <federico.vaga@vaga.pv.it>,
"Stephen Rothwell" <sfr@canb.auug.org.au>,
"Konstantin Ryabitsev" <konstantin@linuxfoundation.org>,
"Matthew Wilcox" <willy@infradead.org>
Subject: Re: [PATCH v2] Documentation: management-style: Reword "had better known the details" phrase
Date: Wed, 27 Aug 2025 21:18:57 -0700 [thread overview]
Message-ID: <d0070beb-f6fd-477c-a315-a2c6db99c227@infradead.org> (raw)
In-Reply-To: <aK_XIoncppxWp7sB@archie.me>
On 8/27/25 9:12 PM, Bagas Sanjaya wrote:
> On Wed, Aug 27, 2025 at 11:33:12AM +0200, Mauro Carvalho Chehab wrote:
>> As a non-native English speaker, "had better know" looks really
>> weird on my eyes, as, at least for me, "know" is a verb.
>>
>> Heh, I just discovered today by looking on a dictionary:
>>
>> https://dictionary.cambridge.org/dictionary/english/know
>>
>> That know can informally be used as a noun (a shortcut for
>> knowledge?).
>>
>> For me as a non-native English speaker, when one writes:
>>
>> They "most likely know" (know here is a verb)
>>
>> or:
>> They "had better knowledge" (knowledge is a name)
>>
>> Things become clearer.
>>
>> Heh:
>>
>> They "had better know the details better than you"
>>
>> the "better" word is used twice, and yeah, this is requires more
>> fluency in English for a non-native speaker to get what it says.
>>
>> Considering that "know" (noun) seems to be a shortcut
>> for "knowledge", what about:
>>
>> They "had better knowledge about the details than you"
>
> That can be alternative.
Nope, afraid not. Just leave it as is or (I think) 2 people have suggested
something like "They should know better about the details than you".
--
~Randy
next prev parent reply other threads:[~2025-08-28 4:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-27 4:48 [PATCH v2] Documentation: management-style: Reword "had better known the details" phrase Bagas Sanjaya
2025-08-27 5:17 ` Randy Dunlap
2025-08-27 5:41 ` Jonathan Corbet
2025-08-27 9:33 ` Mauro Carvalho Chehab
2025-08-27 11:28 ` Jonathan Corbet
2025-08-27 12:48 ` Mauro Carvalho Chehab
2025-08-27 13:05 ` Jonathan Corbet
2025-08-27 13:49 ` Mauro Carvalho Chehab
2025-08-27 14:10 ` Mauro Carvalho Chehab
2025-08-28 4:12 ` Bagas Sanjaya
2025-08-28 4:18 ` Randy Dunlap [this message]
2025-08-28 23:08 ` Bagas Sanjaya
2025-08-28 23:19 ` Laurent Pinchart
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=d0070beb-f6fd-477c-a315-a2c6db99c227@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=konstantin@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=willy@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;
as well as URLs for NNTP newsgroup(s).