From: Steve Sakoman <steve@sakoman.com>
To: bitbake-devel@lists.openembedded.org
Subject: [bitbake][kirkstone][2.0][PATCH 0/3] Patch review
Date: Wed, 8 Nov 2023 12:57:18 -1000 [thread overview]
Message-ID: <cover.1699484095.git.steve@sakoman.com> (raw)
Please review this set of changes for 2.0/kirkstone and have comments back
by end of day Friday, November 10
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/6158
The following changes since commit 6c1ffa9091d0c53a100e8c8c15122d28642034bd:
SECURITY.md: add file (2023-10-24 12:50:43 +0100)
are available in the Git repository at:
https://git.openembedded.org/bitbake-contrib stable/2.0-nut
https://git.openembedded.org/bitbake-contrib/log/?h=stable/2.0-nut
Denys Dmytriyenko (1):
runqueue: convert deferral messages from bb.note to bb.debug
Peter Kjellerstedt (2):
bitbake-getvar: Make --quiet work with --recipe
tinfoil: Do not fail when logging is disabled and full config is used
bin/bitbake-getvar | 5 +++--
lib/bb/runqueue.py | 6 +++---
lib/bb/tinfoil.py | 2 +-
3 files changed, 7 insertions(+), 6 deletions(-)
--
2.34.1
next reply other threads:[~2023-11-08 22:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 22:57 Steve Sakoman [this message]
2023-11-08 22:57 ` [bitbake][kirkstone][2.0][PATCH 1/3] bitbake-getvar: Make --quiet work with --recipe Steve Sakoman
2023-11-08 22:57 ` [bitbake][kirkstone][2.0][PATCH 2/3] tinfoil: Do not fail when logging is disabled and full config is used Steve Sakoman
2023-11-08 22:57 ` [bitbake][kirkstone][2.0][PATCH 3/3] runqueue: convert deferral messages from bb.note to bb.debug Steve Sakoman
-- strict thread matches above, loose matches on Subject: below --
2022-05-23 14:40 [bitbake][kirkstone][2.0][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.1699484095.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