From: Steve Sakoman <steve@sakoman.com>
To: bitbake-devel@lists.openembedded.org
Subject: [bitbake][dunfell][1.46][PATCH 0/3] Patch review
Date: Sun, 28 Nov 2021 12:02:45 -1000 [thread overview]
Message-ID: <cover.1638136822.git.steve@sakoman.com> (raw)
Please review this set of patches for dunfell/1.46 and have comments back by
end of day Tuesday.
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/2968
The following changes since commit c0348de8121c3a842bf44906f7e2f79e93f7275b:
fetch/wget: Add timeout for checkstatus calls (30s) (2021-11-11 10:58:01 +0000)
are available in the Git repository at:
git://git.openembedded.org/bitbake-contrib stable/1.46-nut
http://cgit.openembedded.org/bitbake-contrib/log/?h=stable/1.46-nut
Richard Purdie (3):
command: Ensure exceptions inheriting from BBHandledException are
visible
tinfoil: When sending commands we need to process events
process/knotty: Improve early exception handling
lib/bb/command.py | 6 +++++-
lib/bb/server/process.py | 7 ++++++-
lib/bb/tinfoil.py | 11 ++++++++++-
lib/bb/ui/knotty.py | 21 +++++++++++++++++----
4 files changed, 38 insertions(+), 7 deletions(-)
--
2.25.1
next reply other threads:[~2021-11-28 22:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-28 22:02 Steve Sakoman [this message]
2021-11-28 22:02 ` [bitbake][dunfell][1.46][PATCH 1/3] command: Ensure exceptions inheriting from BBHandledException are visible Steve Sakoman
2021-11-28 22:02 ` [bitbake][dunfell][1.46][PATCH 2/3] tinfoil: When sending commands we need to process events Steve Sakoman
2021-11-28 22:02 ` [bitbake][dunfell][1.46][PATCH 3/3] process/knotty: Improve early exception handling Steve Sakoman
-- strict thread matches above, loose matches on Subject: below --
2023-02-07 15:09 [bitbake][dunfell][1.46][PATCH 0/3] 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.1638136822.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