All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: docs@lists.yoctoproject.org
Subject: [PATCH][scarthgap 2/3] sphinx-lint: missing space after literal
Date: Fri, 23 May 2025 21:10:31 -0400	[thread overview]
Message-ID: <20250524011032.19679-2-twoerner@gmail.com> (raw)
In-Reply-To: <20250524011032.19679-1-twoerner@gmail.com>

Fix all instances of missing-space-after-literal as reported by 'make
sphinx-lint'.

Signed-off-by: Trevor Woerner <twoerner@gmail.com>
---
 documentation/sdk-manual/extensible.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/documentation/sdk-manual/extensible.rst b/documentation/sdk-manual/extensible.rst
index a7546e728849..ab4956f46619 100644
--- a/documentation/sdk-manual/extensible.rst
+++ b/documentation/sdk-manual/extensible.rst
@@ -802,7 +802,7 @@ the two modes:
 
       This instance of VSCode uses plugins that are useful for the development
       of the application. ``devtool ide-sdk`` generates the necessary
-      ``extensions.json``, ``settings.json``, ``tasks.json``and ``launch.json``
+      ``extensions.json``, ``settings.json``, ``tasks.json`` and ``launch.json``
       configuration files for all the involved plugins.
 
       When the source code folder present in the workspace folder is opened in
-- 
2.44.0.501.g19981daefd7c



  reply	other threads:[~2025-05-24  1:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-24  1:10 [PATCH][scarthgap 1/3] sphinx-lint: trailing whitespace Trevor Woerner
2025-05-24  1:10 ` Trevor Woerner [this message]
2025-05-24  1:10 ` [PATCH][scarthgap 3/3] sphinx-lint: unbalanced inline literal markup Trevor Woerner
2025-05-27  6:33 ` [PATCH][scarthgap 1/3] sphinx-lint: trailing whitespace Antonin Godard

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=20250524011032.19679-2-twoerner@gmail.com \
    --to=twoerner@gmail.com \
    --cc=docs@lists.yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.