From: Steve Sakoman <steve@sakoman.com>
To: bitbake-devel@lists.openembedded.org
Subject: [bitbake][kirkstone][2.0][PATCH 0/4] Patch review
Date: Tue, 14 Feb 2023 05:28:40 -1000 [thread overview]
Message-ID: <cover.1676388410.git.steve@sakoman.com> (raw)
Please review this set of patches for 2.0/kirkstone and have comments back by
end of day Thursday.
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/4921
The following changes since commit 86f2fa5261da959cda706c794a0047e5e89d4d6b:
fetch2/git: Clarify the meaning of namespace (2023-02-01 09:03:36 -1000)
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
Etienne Cordonnier (1):
siggen: Fix inefficient string concatenation
Marius Kriegerowski (1):
bitbake-diffsigs: Make PEP8 compliant
Mark Hatle (1):
utils/ply: Update md5 to better report errors with hashlib
Schmidt, Adriaan (1):
bitbake-diffsigs: break on first dependent task difference
bin/bitbake-diffsigs | 49 ++++++++++++++++++++++++--------------------
lib/bb/siggen.py | 11 +++++-----
lib/bb/utils.py | 7 ++++++-
lib/ply/yacc.py | 7 +++++++
4 files changed, 46 insertions(+), 28 deletions(-)
--
2.34.1
next reply other threads:[~2023-02-14 15:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 15:28 Steve Sakoman [this message]
2023-02-14 15:28 ` [bitbake][kirkstone][2.0][PATCH 1/4] siggen: Fix inefficient string concatenation Steve Sakoman
2023-02-14 15:28 ` [bitbake][kirkstone][2.0][PATCH 2/4] utils/ply: Update md5 to better report errors with hashlib Steve Sakoman
2023-02-14 15:28 ` [bitbake][kirkstone][2.0][PATCH 3/4] bitbake-diffsigs: Make PEP8 compliant Steve Sakoman
2023-02-14 15:28 ` [bitbake][kirkstone][2.0][PATCH 4/4] bitbake-diffsigs: break on first dependent task difference Steve Sakoman
-- strict thread matches above, loose matches on Subject: below --
2024-10-05 13:44 [bitbake][kirkstone][2.0][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.1676388410.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.