From: Steve Sakoman <steve@sakoman.com>
To: bitbake-devel@lists.openembedded.org
Subject: [bitbake][scarthgap][2.8][PATCH 0/4] Pull request (cover letter only)
Date: Sat, 8 Mar 2025 06:34:09 -0800 [thread overview]
Message-ID: <cover.1741444400.git.steve@sakoman.com> (raw)
The following changes since commit 7375d32e8c1af20c51abec4eb3b072b4ca58b239:
data_smart.py: clear expand_cache in _setvar_update_overridevars (2025-03-05 19:10:43 +0000)
are available in the Git repository at:
https://git.openembedded.org/bitbake-contrib stable/2.8-next
https://git.openembedded.org/bitbake-contrib/log/?h=stable/2.8-next
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-08 14:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-08 14:34 Steve Sakoman [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-06-18 9:36 [bitbake][scarthgap][2.8][PATCH 0/4] Pull request (cover letter only) Jeremy Rosen
2026-09-16 8:38 Yoann Congal
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.1741444400.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox