($INBOX_DIR/description missing)
 help / color / mirror / Atom feed
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: Enguerrand de Ribaucourt <enguerrand.de-ribaucourt@savoirfairelinux.com>
Cc: docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH] manuals: document VSCode extension
Date: Mon, 8 Jan 2024 17:46:32 +0100	[thread overview]
Message-ID: <7c60e04d-7d44-4ef4-b137-7d2a08afad27@bootlin.com> (raw)
In-Reply-To: <20240102110932.42188-1-enguerrand.de-ribaucourt@savoirfairelinux.com>

Hi Enguerrand

On 02.01.24 at 12:09, Enguerrand de Ribaucourt wrote:
> The VSCode extension is now officially maintained and published by the
> Yocto Project so it should be referenced in the manuals to help users
> discover it.
>
> I located the most relevant places to reference the extension by looking
> at how the old Eclipse plugin was documented in the 2.6 manuals as well
> as the current Toaster references.
>
> Signed-off-by: Enguerrand de Ribaucourt <enguerrand.de-ribaucourt@savoirfairelinux.com>

Many thanks for this update!
Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Applied to master-next, and to be merged soon in master.

I'd also like to backport to other (supported) release branches. Is the 
extension compatible with any version?
Thanks again
Michael.

-- 
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



      reply	other threads:[~2024-01-08 16:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-02 11:09 [PATCH] manuals: document VSCode extension Enguerrand de Ribaucourt
2024-01-08 16:46 ` Michael Opdenacker [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=7c60e04d-7d44-4ef4-b137-7d2a08afad27@bootlin.com \
    --to=michael.opdenacker@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=enguerrand.de-ribaucourt@savoirfairelinux.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).