From: Jonathan Corbet <corbet@lwn.net>
To: Thorsten Blum <thorsten.blum@toblux.com>
Cc: 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: Update syntax highlighting for code-blocks
Date: Mon, 05 Feb 2024 10:22:50 -0700 [thread overview]
Message-ID: <87cytavn9x.fsf@meer.lwn.net> (raw)
In-Reply-To: <20240203223926.5077-1-thorsten.blum@toblux.com>
Thorsten Blum <thorsten.blum@toblux.com> writes:
> Use c and elisp instead of none in code-blocks
>
> Signed-off-by: Thorsten Blum <thorsten.blum@toblux.com>
> ---
> Documentation/process/coding-style.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/process/coding-style.rst b/Documentation/process/coding-style.rst
> index c48382c6b477..a75c7044d8b7 100644
> --- a/Documentation/process/coding-style.rst
> +++ b/Documentation/process/coding-style.rst
> @@ -203,7 +203,7 @@ Do not unnecessarily use braces where a single statement will do.
>
> and
>
> -.. code-block:: none
> +.. code-block:: c
>
> if (condition)
> do_this();
> @@ -660,7 +660,7 @@ make a good program).
> So, you can either get rid of GNU emacs, or change it to use saner
> values. To do the latter, you can stick the following in your .emacs file:
>
> -.. code-block:: none
> +.. code-block:: elisp
Applied, thanks.
jon
prev parent reply other threads:[~2024-02-05 17:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-03 22:39 [PATCH] Documentation: coding-style: Update syntax highlighting for code-blocks Thorsten Blum
2024-02-05 17:22 ` 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=87cytavn9x.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).