Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Steve Sakoman <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][styhead 0/8] Patch review
Date: Wed, 29 Jan 2025 10:04:49 -0800	[thread overview]
Message-ID: <cover.1738173760.git.steve@sakoman.com> (raw)

Please review this set of changes for styhead and have comments back by
end of day Friday, January 31

Passed a-full on autobuilder:

https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/905

The following changes since commit 06439dff5437782f7b6627e0374eaa24ca5aee4a:

  boost: fix do_fetch error (2025-01-23 08:26:01 -0800)

are available in the Git repository at:

  https://git.openembedded.org/openembedded-core-contrib stable/styhead-nut
  https://git.openembedded.org/openembedded-core-contrib/log/?h=stable/styhead-nut

Adrian Freihofer (5):
  devtool: modify support debug-builds
  devtool: ide-sdk sort cmake preset
  devtool: ide-sdk recommend DEBUG_BUILD
  oe-selftest: devtool ide-sdk use modify debug-build
  devtool: ide-sdk remove the plugin from eSDK installer

Peter Marko (3):
  go: upgrade 1.22.8 -> 1.22.9
  go: upgrade 1.22.9 -> 1.22.10
  go: upgrade 1.22.10 -> 1.22.11

 meta/lib/oeqa/selftest/cases/devtool.py       |  2 +-
 .../go/{go-1.22.8.inc => go-1.22.11.inc}      |  2 +-
 ..._1.22.8.bb => go-binary-native_1.22.11.bb} |  6 +-
 ...1.22.8.bb => go-cross-canadian_1.22.11.bb} |  0
 ...go-cross_1.22.8.bb => go-cross_1.22.11.bb} |  0
 ...sssdk_1.22.8.bb => go-crosssdk_1.22.11.bb} |  0
 ...untime_1.22.8.bb => go-runtime_1.22.11.bb} |  0
 .../go/{go_1.22.8.bb => go_1.22.11.bb}        |  0
 scripts/lib/devtool/ide_sdk.py                | 63 ++++++-------------
 scripts/lib/devtool/standard.py               |  3 +
 10 files changed, 28 insertions(+), 48 deletions(-)
 rename meta/recipes-devtools/go/{go-1.22.8.inc => go-1.22.11.inc} (89%)
 rename meta/recipes-devtools/go/{go-binary-native_1.22.8.bb => go-binary-native_1.22.11.bb} (78%)
 rename meta/recipes-devtools/go/{go-cross-canadian_1.22.8.bb => go-cross-canadian_1.22.11.bb} (100%)
 rename meta/recipes-devtools/go/{go-cross_1.22.8.bb => go-cross_1.22.11.bb} (100%)
 rename meta/recipes-devtools/go/{go-crosssdk_1.22.8.bb => go-crosssdk_1.22.11.bb} (100%)
 rename meta/recipes-devtools/go/{go-runtime_1.22.8.bb => go-runtime_1.22.11.bb} (100%)
 rename meta/recipes-devtools/go/{go_1.22.8.bb => go_1.22.11.bb} (100%)

-- 
2.43.0



             reply	other threads:[~2025-01-29 18:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-29 18:04 Steve Sakoman [this message]
2025-01-29 18:04 ` [OE-core][styhead 1/8] go: upgrade 1.22.8 -> 1.22.9 Steve Sakoman
2025-01-29 18:04 ` [OE-core][styhead 2/8] go: upgrade 1.22.9 -> 1.22.10 Steve Sakoman
2025-01-29 18:04 ` [OE-core][styhead 3/8] go: upgrade 1.22.10 -> 1.22.11 Steve Sakoman
2025-01-29 18:04 ` [OE-core][styhead 4/8] devtool: modify support debug-builds Steve Sakoman
2025-01-29 18:04 ` [OE-core][styhead 5/8] devtool: ide-sdk sort cmake preset Steve Sakoman
2025-01-29 18:04 ` [OE-core][styhead 6/8] devtool: ide-sdk recommend DEBUG_BUILD Steve Sakoman
2025-01-29 18:04 ` [OE-core][styhead 7/8] oe-selftest: devtool ide-sdk use modify debug-build Steve Sakoman
2025-01-29 18:04 ` [OE-core][styhead 8/8] devtool: ide-sdk remove the plugin from eSDK installer Steve Sakoman

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=cover.1738173760.git.steve@sakoman.com \
    --to=steve@sakoman.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