public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Adrian Freihofer" <adrian.freihofer@siemens.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [scarthgap 00/15] Patch review
Date: Mon, 13 Jan 2025 14:32:24 -0800	[thread overview]
Message-ID: <27315.1736807544501527525@lists.openembedded.org> (raw)
In-Reply-To: <cover.1736801113.git.steve@sakoman.com>

[-- Attachment #1: Type: text/plain, Size: 834 bytes --]

Hi Steve

Would it be possible to cherry-pick also these poky commits:

a3c51794144 oe-selftest: devtool ide-sdk use modify debug-build
92a4abac54a devtool: ide-sdk recommend DEBUG_BUILD
71acb3b781d devtool: ide-sdk sort cmake preset
1f7eb26c947 devtool: modify support debug-builds

respectively these OE-core commits:

fc17808799d2b667afbe4ea9837b66af70d47007
b886c26bf893878ba8eb6bee80dd0507e5cb0d2d
65950eb601c6c8aac0e4bc8683e544305346229d
a3c5179414410ba8ccf40c7ec168ffbbf73a9096

These patches fix some bugs. They also restore compatibility with the latest version 2.8.0 of https://marketplace.visualstudio.com/items/yocto-project.yocto-bitbake/changelog. Without these patches, the user has to configure the bitbake.disableDevtoolDebugBuild setting, which is not intuitive at all.

Thank you anyway.
Adrian

[-- Attachment #2: Type: text/html, Size: 1067 bytes --]

  parent reply	other threads:[~2025-01-13 22:32 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-13 20:46 [OE-core][scarthgap 00/15] Patch review Steve Sakoman
2025-01-13 20:46 ` [OE-core][scarthgap 01/15] cve-update-nvd2-native: Handle BB_NO_NETWORK and missing db Steve Sakoman
2025-01-13 20:46 ` [OE-core][scarthgap 02/15] linux-yocto/6.6: update to v6.6.56 Steve Sakoman
2025-01-13 20:46 ` [OE-core][scarthgap 03/15] linux-yocto/6.6: update to v6.6.58 Steve Sakoman
2025-01-13 20:46 ` [OE-core][scarthgap 04/15] linux-yocto/6.6: genericarm64.cfg: enable CONFIG_DMA_CMA Steve Sakoman
2025-01-13 20:46 ` [OE-core][scarthgap 05/15] linux-yocto/6.6: update to v6.6.59 Steve Sakoman
2025-01-13 20:46 ` [OE-core][scarthgap 06/15] linux-yocto/6.6: update to v6.6.60 Steve Sakoman
2025-01-13 20:46 ` [OE-core][scarthgap 07/15] linux-yocto/6.6: update to v6.6.62 Steve Sakoman
2025-01-13 20:47 ` [OE-core][scarthgap 08/15] linux-yocto/6.6: bsp/genericarm64: disable ARM64_SME Steve Sakoman
2025-01-13 20:47 ` [OE-core][scarthgap 09/15] linux-yocto/6.6: update to v6.6.63 Steve Sakoman
2025-01-13 20:47 ` [OE-core][scarthgap 10/15] linux-yocto/6.6: update to v6.6.64 Steve Sakoman
2025-01-13 20:47 ` [OE-core][scarthgap 11/15] linux-yocto/6.6: update to v6.6.66 Steve Sakoman
2025-01-13 20:47 ` [OE-core][scarthgap 12/15] linux-yocto/6.6: update to v6.6.69 Steve Sakoman
2025-01-13 21:08   ` Patchtest results for " patchtest
2025-01-13 20:47 ` [OE-core][scarthgap 13/15] groff: Fix race issues for parallel build Steve Sakoman
2025-01-13 20:47 ` [OE-core][scarthgap 14/15] bluez5: backport patch to fix address type when loading keys Steve Sakoman
2025-01-13 20:47 ` [OE-core][scarthgap 15/15] systemd: enable create-log-dirs Steve Sakoman
2025-01-13 22:32 ` Adrian Freihofer [this message]
2025-01-14 15:56   ` [OE-core] [scarthgap 00/15] Patch review Steve Sakoman
2025-01-14 16:31     ` Adrian Freihofer

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=27315.1736807544501527525@lists.openembedded.org \
    --to=adrian.freihofer@siemens.com \
    --cc=openembedded-core@lists.openembedded.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