From: Jonathan Corbet <corbet@lwn.net>
To: Thorsten Blum <thorsten.blum@toblux.com>
Cc: Federico Vaga <federico.vaga@vaga.pv.it>,
Carlos Bilbao <carlos.bilbao@amd.com>,
Avadhut Naik <avadhut.naik@amd.com>, Alex Shi <alexs@kernel.org>,
Yanteng Si <siyanteng@loongson.cn>,
Hu Haowen <2023002089@link.tyut.edu.cn>,
workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Thorsten Blum <thorsten.blum@toblux.com>
Subject: Re: [PATCH] Documentation: coding-style: Fix indentation in code-blocks
Date: Mon, 05 Feb 2024 10:16:33 -0700 [thread overview]
Message-ID: <87le7yvnke.fsf@meer.lwn.net> (raw)
In-Reply-To: <20240202231316.7606-1-thorsten.blum@toblux.com>
Thorsten Blum <thorsten.blum@toblux.com> writes:
> - Remove spaces in C code-blocks to align error labels consistently
> - Replace tab characters with spaces in emacs-lisp code blocks
>
> Signed-off-by: Thorsten Blum <thorsten.blum@toblux.com>
> ---
> Documentation/process/coding-style.rst | 6 +++---
> Documentation/translations/it_IT/process/coding-style.rst | 6 +++---
> Documentation/translations/sp_SP/process/coding-style.rst | 6 +++---
> Documentation/translations/zh_CN/process/coding-style.rst | 4 ++--
> Documentation/translations/zh_TW/process/coding-style.rst | 4 ++--
> 5 files changed, 13 insertions(+), 13 deletions(-)
I have applied this, but I would really rather not see a lot of
white-space patches like this; there are so many ways in which our
documentation could use improvement, and this is pretty far down the
list.
Thanks,
jon
prev parent reply other threads:[~2024-02-05 17:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 23:13 [PATCH] Documentation: coding-style: Fix indentation in code-blocks Thorsten Blum
2024-02-05 17:16 ` 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=87le7yvnke.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=2023002089@link.tyut.edu.cn \
--cc=alexs@kernel.org \
--cc=avadhut.naik@amd.com \
--cc=carlos.bilbao@amd.com \
--cc=federico.vaga@vaga.pv.it \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=siyanteng@loongson.cn \
--cc=thorsten.blum@toblux.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).