From: Jonathan Corbet <corbet@lwn.net>
To: Wojciech <wojciech.develop@gmail.com>, adobriyan@gmail.com
Cc: linux-doc@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] docs: proc: fix double whitespace
Date: Sat, 14 Feb 2026 07:57:03 -0700 [thread overview]
Message-ID: <87v7fzqsow.fsf@trenco.lwn.net> (raw)
In-Reply-To: <CALGt97-amOrBjW0LStyJSoT=n0TsR8nbEuE8rk7ME4joq51+5w@mail.gmail.com>
Thank you for working to improve our documentation.
FWIW, there must be a lot of places where proc.rst is need of actual
updates.
Wojciech <wojciech.develop@gmail.com> writes:
> From 67259d718da986c176cb45f861a43eb04dfc481b Mon Sep 17 00:00:00 2001
> From: "Wojciech S." <wojciech.develop@gmail.com>
> Date: Sat, 14 Feb 2026 09:51:35 +0100
> Subject: [PATCH] docs: proc: fix double whitespace
>
> v2: Corrected Signed-off-by email address.
> Remove an unintended double whitespace in proc.rst.
So none of this belongs in the changelog; the changes in this version
can be noted below the "---" line, but the email headers simply should
not be here.
Overall: it seems clear that, at some point, somebody wanted this
document to be right-justified. I agree that's not too helpful and need
not be there. But: "two spaces after a period" is explicitly not an
error in the kernel docs and need not be "corrected". Avoiding those
changes would reduce the churn here considerably.
Thanks,
jon
prev parent reply other threads:[~2026-02-14 14:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-14 12:47 [PATCH v2] docs: proc: fix double whitespace Wojciech
2026-02-14 14:57 ` 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=87v7fzqsow.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=adobriyan@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wojciech.develop@gmail.com \
/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