From: Steve Sakoman <steve@sakoman.com>
To: bitbake-devel@lists.openembedded.org
Subject: [bitbake][walnascar][2.12][PATCH 0/2] Patch review
Date: Wed, 10 Sep 2025 08:55:08 -0700 [thread overview]
Message-ID: <cover.1757519577.git.steve@sakoman.com> (raw)
Please review this set of changes for 2.12/walnascar and have comments back
by end of day Friday, September 12
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/2348
The following changes since commit 710f98844ae30416bdf6a01b655df398b49574ec:
utils: Optimise signal/sigmask performance (2025-07-31 09:32:00 -0700)
are available in the Git repository at:
https://git.openembedded.org/bitbake-contrib stable/2.12-nut
https://git.openembedded.org/bitbake-contrib/log/?h=stable/2.12-nut
Joshua Watt (1):
Use a "fork" multiprocessing context
Martin Jansa (1):
bitbake: Bump version to 2.12.1
bin/bitbake | 2 +-
lib/bb/__init__.py | 30 +++++++++++++++++++++++++++++-
lib/bb/asyncrpc/serv.py | 2 +-
lib/bb/cooker.py | 2 +-
lib/bb/server/process.py | 2 +-
lib/bb/tests/support/httpserver.py | 4 ++--
lib/bb/utils.py | 4 +---
lib/hashserv/tests.py | 2 +-
8 files changed, 37 insertions(+), 11 deletions(-)
--
2.43.0
next reply other threads:[~2025-09-10 15:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 15:55 Steve Sakoman [this message]
2025-09-10 15:55 ` [bitbake][walnascar][2.12][PATCH 1/2] Use a "fork" multiprocessing context Steve Sakoman
2025-09-10 15:55 ` [bitbake][walnascar][2.12][PATCH 2/2] bitbake: Bump version to 2.12.1 Steve Sakoman
2025-09-17 7:27 ` [bitbake-devel] " Martin Jansa
2025-09-17 13:57 ` Steve Sakoman
2025-09-17 14:05 ` Martin Jansa
2025-09-17 16:25 ` Steve Sakoman
2025-09-17 22:34 ` Richard Purdie
2025-09-17 22:35 ` Steve Sakoman
2025-09-17 22:24 ` Richard Purdie
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.1757519577.git.steve@sakoman.com \
--to=steve@sakoman.com \
--cc=bitbake-devel@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 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.