From: Steve Sakoman <steve@sakoman.com>
To: bitbake-devel@lists.openembedded.org
Subject: [bitbake][scarthgap][2.8][PATCH 0/3] Patch review
Date: Tue, 21 Jan 2025 19:08:43 -0800 [thread overview]
Message-ID: <cover.1737515198.git.steve@sakoman.com> (raw)
Please reviwe this set of changes for 2.8/scarthgap and have comments back
by end of day Thursday, January 23
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/856
The following changes since commit f40a3a477d5241b697bf2fb030dd804c1ff5839f:
runqueue: Fix scenetask processing performance issue (2024-12-03 06:34:38 -0800)
are available in the Git repository at:
https://git.openembedded.org/bitbake-contrib stable/2.8-nut
https://git.openembedded.org/bitbake-contrib/log/?h=stable/2.8-nut
Chris Laplante (3):
ui/knotty: print log paths for failed tasks in summary
ui/knotty: respect NO_COLOR & check for tty; rename print_hyperlink =>
format_hyperlink
cooker: Make cooker 'skiplist' per-multiconfig/mc
lib/bb/command.py | 21 ++++++++++++++++++---
lib/bb/cooker.py | 11 ++++++-----
lib/bb/tinfoil.py | 16 ++++++++++++----
lib/bb/ui/knotty.py | 20 +++++++++++++++++---
lib/bblayers/query.py | 14 +++++++-------
5 files changed, 60 insertions(+), 22 deletions(-)
--
2.43.0
next reply other threads:[~2025-01-22 3:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 3:08 Steve Sakoman [this message]
2025-01-22 3:08 ` [bitbake][scarthgap][2.8][PATCH 1/3] ui/knotty: print log paths for failed tasks in summary Steve Sakoman
2025-01-22 3:08 ` [bitbake][scarthgap][2.8][PATCH 2/3] ui/knotty: respect NO_COLOR & check for tty; rename print_hyperlink => format_hyperlink Steve Sakoman
2025-01-22 3:08 ` [bitbake][scarthgap][2.8][PATCH 3/3] cooker: Make cooker 'skiplist' per-multiconfig/mc Steve Sakoman
-- strict thread matches above, loose matches on Subject: below --
2024-12-04 20:33 [bitbake][scarthgap][2.8][PATCH 0/3] Patch review Steve Sakoman
2024-06-17 12:23 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.1737515198.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.