From: Jonathan Corbet <corbet@lwn.net>
To: Joel Savitz <jsavitz@redhat.com>, linux-kernel@vger.kernel.org
Cc: Joel Savitz <jsavitz@redhat.com>, linux-doc@vger.kernel.org
Subject: Re: [PATCH v3] docs: namespace: Tweak and reword resource control doc
Date: Mon, 28 Apr 2025 18:01:22 -0600 [thread overview]
Message-ID: <87frhrrg31.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250421161723.1138903-1-jsavitz@redhat.com>
Joel Savitz <jsavitz@redhat.com> writes:
> Fix the document title and reword the phrasing to active voice.
>
> Signed-off-by: Joel Savitz <jsavitz@redhat.com>
> ---
> Changes since v2:
> - Fix another typo
> Changes since v1:
> - Fix spelling of resource
>
> .../namespaces/resource-control.rst | 24 +++++++++----------
> 1 file changed, 12 insertions(+), 12 deletions(-)
I've applied this. As a general rule, though, "switch to active voice"
is the sort of churn that is best avoided unless you're making more
substantive changes. We have a lot of far more pressing problems in the
docs...
Thanks,
jon
prev parent reply other threads:[~2025-04-29 0:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-21 16:17 [PATCH v3] docs: namespace: Tweak and reword resource control doc Joel Savitz
2025-04-28 12:54 ` Joel Savitz
2025-04-28 14:28 ` Bagas Sanjaya
2025-04-29 0:01 ` Jonathan Corbet [this message]
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=87frhrrg31.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=jsavitz@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@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