From: Steve Sakoman <steve@sakoman.com>
To: bitbake-devel@lists.openembedded.org
Subject: [bitbake][dunfell][1.46][PATCH 00/14] Pull request (cover letter only)
Date: Tue, 28 Sep 2021 13:20:35 -1000 [thread overview]
Message-ID: <cover.1632871177.git.steve@sakoman.com> (raw)
The following changes since commit 3c1799b2576f80b6dcb310e03f77105a58b9fa8e:
tests/fetch2: Use our own git server for dtc test repo (2021-09-22 22:45:10 +0100)
are available in the Git repository at:
git://git.openembedded.org/bitbake-contrib stable/1.46-next
http://cgit.openembedded.org/bitbake-contrib/log/?h=stable/1.46-next
Joshua Watt (1):
server: Fix early parsing errors preventing zombie bitbake
Marco Felsch (1):
bitbake: bitbake-layers: add skip reason to output
Richard Purdie (12):
ui/taskexp: Improve startup exception handling
ui/taskexp: Fix to work with empty build directories
build: Match markup to real function name
build: Handle SystemExit in python tasks correctly
process: Don't include logs in error message if piping them
build: Avoid duplicating logs in verbose mode
build: Catch and error upon circular task references
data_smart: Improve error display for handled exceptions
cookerdata: Improve missing core layer error message
cookerdata: Show error for no BBLAYERS in bblayers.conf
bitbake-worker: Improve error handling
cookerdata: Show a readable error for invalid multiconfig name
bin/bitbake-worker | 10 ++++++----
lib/bb/build.py | 12 +++++++++---
lib/bb/cookerdata.py | 7 +++++++
lib/bb/data_smart.py | 2 ++
lib/bb/process.py | 3 +++
lib/bb/server/process.py | 3 ++-
lib/bb/ui/taskexp.py | 5 +++++
lib/bblayers/query.py | 2 +-
8 files changed, 35 insertions(+), 9 deletions(-)
--
2.25.1
reply other threads:[~2021-09-28 23:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.1632871177.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.