From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Adrian Freihofer" <adrian.freihofer@gmail.com>,
<docs@lists.yoctoproject.org>
Subject: Re: [scarthgap,styhead][PATCH 1/1] sdk-manual: extensible.rst: update devtool ide-sdk
Date: Mon, 27 Jan 2025 11:27:43 +0100 [thread overview]
Message-ID: <D7CS8UUTIV3V.3G2ID84LSE4PX@bootlin.com> (raw)
In-Reply-To: <a8dfa467700d8d7961bb24bb5c52290b077d8d5b.camel@gmail.com>
Hi Adrian,
On Mon Jan 27, 2025 at 11:18 AM CET, Adrian Freihofer wrote:
> Hi Antonin
>
> It's a bit complicated to keep yocto-docs, oe-core and the bitbake
> VSCode plugin consistent by sending patches to different mailing list
> and different people. The related patch series for oe-core is here:
> https://lists.openembedded.org/g/openembedded-core/message/210279.
>
> There are multiple reasons, why I would like to update all the branches
> to the same level:
> * Latest VSCode plugin does devtool modify --debug-build by default.
> With a poky without this option, the user has to take manual action.
> * It's a bug which should be fixed
> * It's without risk for breaking something, it's a trivial change.
>
> So probably yocto-docs needs to wait until oe-core decides and then
> follow. Is this possible?
Sorry, I hadn't noticed that you also sent backports on oe-core. I'll try to
monitor this and make sure the doc patch also gets backported. Feel free to
bounce it if I forget. ;)
Thank you!
Antonin
--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2025-01-27 10:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-26 12:53 [scarthgap,styhead][PATCH 0/1] docs covering pick devtool ide-sdk fixes Adrian Freihofer
2025-01-26 12:53 ` [scarthgap,styhead][PATCH 1/1] sdk-manual: extensible.rst: update devtool ide-sdk Adrian Freihofer
2025-01-27 8:35 ` Antonin Godard
2025-01-27 10:18 ` Adrian Freihofer
2025-01-27 10:27 ` Antonin Godard [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=D7CS8UUTIV3V.3G2ID84LSE4PX@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=adrian.freihofer@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.