From: Steve Sakoman <steve@sakoman.com>
To: bitbake-devel@lists.openembedded.org
Subject: [bitbake][dunfell][1.46][PATCH 0/2] Patch review
Date: Thu, 13 Jan 2022 04:10:12 -1000 [thread overview]
Message-ID: <cover.1642082551.git.steve@sakoman.com> (raw)
Please review this set of patches for dunfell/1.46 and have comments back by
end of day Monday.
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/3112
The following changes since commit c5969eedd035648e3258bade386cc67ce3bb0e03:
cooker/command: Add a dummy event for tinfoil testing (2022-01-07 23:43:41 +0000)
are available in the Git repository at:
git://git.openembedded.org/bitbake-contrib stable/1.46-nut
http://cgit.openembedded.org/bitbake-contrib/log/?h=stable/1.46-nut
Richard Purdie (2):
utils: Update to use exec_module() instead of load_module()
tests/fetch: Drop gnu urls from wget connectivity test
lib/bb/tests/fetch.py | 3 ---
lib/bb/utils.py | 7 +++++--
2 files changed, 5 insertions(+), 5 deletions(-)
--
2.25.1
next reply other threads:[~2022-01-13 14:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 14:10 Steve Sakoman [this message]
2022-01-13 14:10 ` [bitbake][dunfell][1.46][PATCH 1/2] utils: Update to use exec_module() instead of load_module() Steve Sakoman
2022-01-13 14:10 ` [bitbake][dunfell][1.46][PATCH 2/2] tests/fetch: Drop gnu urls from wget connectivity test Steve Sakoman
-- strict thread matches above, loose matches on Subject: below --
2022-11-19 17:51 [bitbake][dunfell][1.46][PATCH 0/2] Patch review Steve Sakoman
2022-03-27 16:43 Steve Sakoman
2021-12-03 18:27 Steve Sakoman
2021-11-04 14:11 Steve Sakoman
2021-10-22 13:59 Steve Sakoman
2021-03-13 19:04 Steve Sakoman
2020-10-12 15:07 Steve Sakoman
2020-09-14 14:19 Steve Sakoman
2020-07-28 22:58 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.1642082551.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