From: Jonathan Corbet <corbet@lwn.net>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.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>,
"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
"Fox Foster" <fox@tardis.ed.ac.uk>,
"Federico Vaga" <federico.vaga@vaga.pv.it>,
"Randy Dunlap" <rdunlap@infradead.org>,
"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 07:05:27 -0600 [thread overview]
Message-ID: <87tt1s9ap4.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250827144757.26599d50@foz.lan>
Mauro Carvalho Chehab <mchehab+huawei@kernel.org> writes:
>> But neither of those say the same thing. Read "had better know" as
>> "really should know" and you get a lot closer. I guess I didn't realize
>> that it was such a strange construction.
>
> I bet very few non-native English speaker developers would understand it
> like that.
Even though a non-native developer wrote it :)
We can tweak it, but I'd rather not change the meaning, and, more to the
point, that document needs significant work rather than low-level
tweaking.
jon
next prev parent reply other threads:[~2025-08-27 13:05 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 [this message]
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
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=87tt1s9ap4.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=mchehab+huawei@kernel.org \
--cc=rdunlap@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.