From: Steve Sakoman <steve@sakoman.com>
To: bitbake-devel@lists.openembedded.org
Subject: [bitbake][kirkstone][2.0][PATCH 0/8] Patch review
Date: Tue, 4 Oct 2022 05:54:51 -1000 [thread overview]
Message-ID: <cover.1664898736.git.steve@sakoman.com> (raw)
Please review this set of patches for kirkstone/2.0 and have comments back
by end of day Wednesday.
Passded a-full on autobuilder:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/4294
The following changes since commit ac576d6fad6bba0cfea931883f25264ea83747ca:
bitbake-user-manual: npm fetcher: improve description of SRC_URI format (2022-09-16 17:52:26 +0100)
are available in the Git repository at:
https://git.openembedded.org/bitbake-contrib stable/2.0-nut
http://cgit.openembedded.org/bitbake-contrib/log/?h=stable/2.0-nut
Joshua Watt (1):
siggen: Fix insufficent entropy in sigtask file names
Neil Horman (1):
Fix npm to use https rather than http
Pavel Zhukov (1):
gitsm: Error out if submodule refers to parent repo
Richard Purdie (5):
runqueue: Ensure deferred tasks are sorted by multiconfig
runqueue: Improve deadlock warning messages
runqueue: Drop deadlock breaking force fail
bitbake: Add copyright headers where missing
asyncrpc/client: Fix unix domain socket chdir race issues
bin/bitbake-prserv | 2 ++
bin/bitbake-worker | 2 ++
bin/git-make-shallow | 2 ++
lib/bb/COW.py | 2 ++
lib/bb/asyncrpc/__init__.py | 2 ++
lib/bb/asyncrpc/client.py | 24 +++++++++++++++---------
lib/bb/asyncrpc/serv.py | 2 ++
lib/bb/codeparser.py | 2 ++
lib/bb/compress/_pipecompress.py | 2 ++
lib/bb/compress/lz4.py | 2 ++
lib/bb/compress/zstd.py | 2 ++
lib/bb/daemonize.py | 2 ++
lib/bb/exceptions.py | 2 ++
lib/bb/fetch2/gitsm.py | 3 +++
lib/bb/fetch2/npm.py | 2 +-
lib/bb/fetch2/osc.py | 2 ++
lib/bb/process.py | 2 ++
lib/bb/runqueue.py | 20 +++++++++++---------
lib/bb/siggen.py | 4 +++-
lib/bb/tests/compression.py | 2 ++
lib/bb/tests/cooker.py | 2 ++
lib/bb/utils.py | 21 +++++++++++++++++++++
lib/bblayers/__init__.py | 2 ++
lib/bblayers/action.py | 2 ++
lib/bblayers/common.py | 2 ++
lib/bblayers/layerindex.py | 2 ++
lib/bblayers/query.py | 2 ++
lib/prserv/__init__.py | 2 ++
lib/prserv/client.py | 2 ++
lib/prserv/db.py | 2 ++
lib/prserv/serv.py | 2 ++
lib/toaster/manage.py | 2 ++
32 files changed, 106 insertions(+), 20 deletions(-)
--
2.25.1
next reply other threads:[~2022-10-04 15:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 15:54 Steve Sakoman [this message]
2022-10-04 15:54 ` [bitbake][kirkstone][2.0][PATCH 1/8] runqueue: Ensure deferred tasks are sorted by multiconfig Steve Sakoman
2022-10-04 15:54 ` [bitbake][kirkstone][2.0][PATCH 2/8] runqueue: Improve deadlock warning messages Steve Sakoman
2022-10-04 15:54 ` [bitbake][kirkstone][2.0][PATCH 3/8] runqueue: Drop deadlock breaking force fail Steve Sakoman
2022-10-04 15:54 ` [bitbake][kirkstone][2.0][PATCH 4/8] siggen: Fix insufficent entropy in sigtask file names Steve Sakoman
2022-10-04 15:54 ` [bitbake][kirkstone][2.0][PATCH 5/8] bitbake: Add copyright headers where missing Steve Sakoman
2022-10-04 15:54 ` [bitbake][kirkstone][2.0][PATCH 6/8] Fix npm to use https rather than http Steve Sakoman
2022-10-04 15:54 ` [bitbake][kirkstone][2.0][PATCH 7/8] gitsm: Error out if submodule refers to parent repo Steve Sakoman
2022-10-04 15:54 ` [bitbake][kirkstone][2.0][PATCH 8/8] asyncrpc/client: Fix unix domain socket chdir race issues 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.1664898736.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.