From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Alexander Kanavin <alex@linutronix.de>, docs@lists.yoctoproject.org
Subject: Re: [docs] [kirkstone][PATCH] sdk-manual: extensible.rst: remove instructions for using SDK functionality directly in a yocto build
Date: Wed, 22 Nov 2023 21:14:19 +0100 [thread overview]
Message-ID: <5f70073d-df1a-4da9-95f6-60c54af9d590@bootlin.com> (raw)
In-Reply-To: <20231122124248.3820970-1-alex@linutronix.de>
Hi Alex,
On 22.11.23 at 13:42, Alexander Kanavin wrote:
> This was not actually backported to kirkstone (and isn't going to be)
> but the documentation for the feature erroneously did make its way
> from master into kirkstone.
>
> Signed-off-by: Alexander Kanavin <alex@linutronix.de>
My fault. Thanks for correcting this mistake.
Merged into "kirkstone".
Cheers
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2023-11-22 20:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 12:42 [kirkstone][PATCH] sdk-manual: extensible.rst: remove instructions for using SDK functionality directly in a yocto build Alexander Kanavin
2023-11-22 20:14 ` 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=5f70073d-df1a-4da9-95f6-60c54af9d590@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=alex.kanavin@gmail.com \
--cc=alex@linutronix.de \
--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 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).