From: Yoann Congal <yoann.congal@smile.fr>
To: bitbake-devel@lists.openembedded.org
Cc: Paul Barker <paul@pbarker.dev>
Subject: [bitbake][scarthgap][2.8][PATCH 0/1] Pull request (cover letter only)
Date: Tue, 10 Mar 2026 23:55:56 +0100 [thread overview]
Message-ID: <cover.1773183271.git.yoann.congal@smile.fr> (raw)
Those are the patches from the last patch review:
https://lore.kernel.org/bitbake-devel/cover.1772924048.git.yoann.congal@smile.fr/T/#t
(no change during review)
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/3349
Ignore the warning about Centos Stream9 (it's support is a work in progress)
The following changes since commit 10118785e4a670bce4980e1044c0888a8b6e84af:
knotty: Make sure getTerminalColumns() returns two integers (2026-02-13 08:48:40 +0000)
are available in the Git repository at:
https://git.openembedded.org/bitbake-contrib stable/2.8-next
https://git.openembedded.org/bitbake-contrib/log/?h=stable/2.8-next
for you to fetch changes up to bebecffef63a3ac60420b5347d549f71b00dc151:
COW: Fix hardcoded magic numbers and work with python 3.13 (2026-03-06 21:15:02 +0100)
----------------------------------------------------------------
Richard Purdie (1):
COW: Fix hardcoded magic numbers and work with python 3.13
lib/bb/COW.py | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
next reply other threads:[~2026-03-10 22:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 22:55 Yoann Congal [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-09-25 14:36 [bitbake][scarthgap][2.8][PATCH 0/1] Pull request (cover letter only) Steve Sakoman
2025-06-04 15:36 Steve Sakoman
2024-10-23 15:40 Steve Sakoman
2024-08-19 13:14 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.1773183271.git.yoann.congal@smile.fr \
--to=yoann.congal@smile.fr \
--cc=bitbake-devel@lists.openembedded.org \
--cc=paul@pbarker.dev \
/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.