From: Steve Sakoman <steve@sakoman.com>
To: bitbake-devel@lists.openembedded.org
Subject: [bitbake][styhead][2.10][PATCH 0/4] Patch review
Date: Fri, 7 Mar 2025 05:54:50 -0800 [thread overview]
Message-ID: <cover.1741355508.git.steve@sakoman.com> (raw)
Please review this set of changes for 2.10/styhead and have comments back
by end of day Monday, March 10
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/1138
The following changes since commit 58e5c70a0572ff5994dc181694e05cd5d3ddaf66:
bblayers/query: Fix using "removeprefix" string method (2025-02-21 13:14:07 +0000)
are available in the Git repository at:
https://git.openembedded.org/bitbake-contrib stable/2.10-nut
https://git.openembedded.org/bitbake-contrib/log/?h=stable/2.10-nut
Richard Purdie (4):
utils: Print information about lock issue before exiting
utils: Tweak lock_timeout logic
utils: Add signal blocking for lock_timeout
event/utils: Avoid deadlock from lock_timeout() and recursive events
lib/bb/event.py | 10 +++++++++-
lib/bb/utils.py | 20 +++++++++++++++++++-
2 files changed, 28 insertions(+), 2 deletions(-)
--
2.43.0
next reply other threads:[~2025-03-07 13:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 13:54 Steve Sakoman [this message]
2025-03-07 13:54 ` [bitbake][styhead][2.10][PATCH 1/4] utils: Print information about lock issue before exiting Steve Sakoman
2025-03-07 13:54 ` [bitbake][styhead][2.10][PATCH 2/4] utils: Tweak lock_timeout logic Steve Sakoman
2025-03-07 13:54 ` [bitbake][styhead][2.10][PATCH 3/4] utils: Add signal blocking for lock_timeout Steve Sakoman
2025-03-07 13:54 ` [bitbake][styhead][2.10][PATCH 4/4] event/utils: Avoid deadlock from lock_timeout() and recursive events Steve Sakoman
-- strict thread matches above, loose matches on Subject: below --
2024-10-30 16:01 [bitbake][styhead][2.10][PATCH 0/4] Patch review 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.1741355508.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.