From: Jonathan Corbet <corbet@lwn.net>
To: I Viswanath <viswanathiyyappan@gmail.com>
Cc: workflows@vger.kernel.org, linux-doc@vger.kernel.org,
skhan@linuxfoundation.org, linux-kernel-mentees@lists.linux.dev,
I Viswanath <viswanathiyyappan@gmail.com>
Subject: Re: [PATCH] Documentation: process: Fix grammar errors in management-style.rst
Date: Sun, 24 Aug 2025 23:10:29 -0600 [thread overview]
Message-ID: <87y0r8c7ga.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250824185015.6312-1-viswanathiyyappan@gmail.com>
I Viswanath <viswanathiyyappan@gmail.com> writes:
> Fix various grammatical errors in management-style.rst
>
> Signed-off-by: I Viswanath <viswanathiyyappan@gmail.com>
Thank you for working to improve our documentation...I don't think I can
apply this patch, though.
Your signoff should include your full name, please.
But more importantly...
> ---
> Documentation/process/management-style.rst | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/process/management-style.rst b/Documentation/process/management-style.rst
> index dfbc69bf49d4..4ae05a89950a 100644
> --- a/Documentation/process/management-style.rst
> +++ b/Documentation/process/management-style.rst
> @@ -15,8 +15,8 @@ to do with reality. It started as a lark, but that doesn't mean that it
> might not actually be true. You'll have to decide for yourself.
>
> Btw, when talking about "kernel manager", it's all about the technical
> -lead persons, not the people who do traditional management inside
> -companies. If you sign purchase orders or you have any clue about the
> +leads, not those who do traditional management inside
> +companies. If you sign purchase orders or have any clue about the
This change is OK, but what was there was OK too
> budget of your group, you're almost certainly not a kernel manager.
> These suggestions may or may not apply to you.
>
> @@ -42,9 +42,9 @@ 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 better know the details better than you; if they come to
This one changes the meaning of the sentence
> you for a technical decision, you're screwed. You're clearly not
> -competent to make that decision for them.
> +competent enough to make that decision for them.
...and this one was fine as it was.
> (Corollary:if the people you manage don't know the details better than
> you, you're also screwed, although for a totally different reason.
> --
In general, this kind of playing with the wording for text that is not
actually wrong is not hugely helpful; I would encourage you to look
elsewhere for places to contribute to the documentation.
Thanks,
jon
next prev parent reply other threads:[~2025-08-25 5:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-24 18:50 I Viswanath
2025-08-25 5:10 ` Jonathan Corbet [this message]
2025-08-25 17:17 ` viswanath
2025-08-26 0:00 ` Bagas Sanjaya
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=87y0r8c7ga.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=skhan@linuxfoundation.org \
--cc=viswanathiyyappan@gmail.com \
--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