From: Randy Dunlap <rdunlap@infradead.org>
To: Addison English <addison.englishw@gmail.com>,
Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org
Subject: Re: [PATCH v2] docs: fix typo in clang-format documentation
Date: Sun, 7 Dec 2025 23:02:51 -0800 [thread overview]
Message-ID: <41f5b115-1725-46d1-a959-db3a5703458d@infradead.org> (raw)
In-Reply-To: <20251208065136.9092-1-addison.englishw@gmail.com>
On 12/7/25 10:51 PM, Addison English wrote:
> The clang-format documentation contains a minor spelling issue where
> "intended" is used instead of "indented" when describing deeply nested
> code. This patch corrects the typo to improve the clarity and consistency.
>
> Signed-off-by: Addison English <addison.englishw@gmail.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
(again)
> ---
> Documentation/dev-tools/clang-format.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/dev-tools/clang-format.rst b/Documentation/dev-tools/clang-format.rst
> index 1d089a847c1b..6c8a0df5a00c 100644
> --- a/Documentation/dev-tools/clang-format.rst
> +++ b/Documentation/dev-tools/clang-format.rst
> @@ -88,7 +88,7 @@ Reformatting blocks of code
>
> By using an integration with your text editor, you can reformat arbitrary
> blocks (selections) of code with a single keystroke. This is specially
> -useful when moving code around, for complex code that is deeply intended,
> +useful when moving code around, for complex code that is deeply indented,
> for multi-line macros (and aligning their backslashes), etc.
>
> Remember that you can always tweak the changes afterwards in those cases
--
~Randy
prev parent reply other threads:[~2025-12-08 7:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-08 6:51 [PATCH v2] docs: fix typo in clang-format documentation Addison English
2025-12-08 7:02 ` Randy Dunlap [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=41f5b115-1725-46d1-a959-db3a5703458d@infradead.org \
--to=rdunlap@infradead.org \
--cc=addison.englishw@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@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 NNTP newsgroup(s).