From: Steve Sakoman <steve@sakoman.com>
To: bitbake-devel@lists.openembedded.org
Subject: [bitbake][kirkstone][2.0][PATCH 0/3] Patch review
Date: Mon, 23 May 2022 04:40:02 -1000 [thread overview]
Message-ID: <cover.1653314792.git.steve@sakoman.com> (raw)
Please review this set of patches for kirkstone/2.0 and have comments back
by end of day Wednesday.
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/3692
The following changes since commit 59c16ae6c55c607c56efd2287537a1b97ba2bf52:
fetch/git : Use cat as pager (2022-05-12 13:41:35 +0100)
are available in the Git repository at:
git://git.openembedded.org/bitbake-contrib stable/2.0-nut
http://cgit.openembedded.org/bitbake-contrib/log/?h=stable/2.0-nut
Gunjan Gupta (1):
fetch2/osc: Small fixes for osc fetcher
Richard Purdie (1):
build: Add clean_stamp API function to allow removal of task stamps
Tomasz Dziendzielski (1):
data: Do not depend on vardepvalueexclude flag
lib/bb/build.py | 14 +++++++++-----
lib/bb/data.py | 2 ++
lib/bb/fetch2/osc.py | 16 ++++++++++------
3 files changed, 21 insertions(+), 11 deletions(-)
--
2.25.1
next reply other threads:[~2022-05-23 14:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-23 14:40 Steve Sakoman [this message]
2022-05-23 14:40 ` [bitbake][kirkstone][2.0][PATCH 1/3] fetch2/osc: Small fixes for osc fetcher Steve Sakoman
2022-05-23 14:40 ` [bitbake][kirkstone][2.0][PATCH 2/3] data: Do not depend on vardepvalueexclude flag Steve Sakoman
2022-05-23 14:40 ` [bitbake][kirkstone][2.0][PATCH 3/3] build: Add clean_stamp API function to allow removal of task stamps Steve Sakoman
-- strict thread matches above, loose matches on Subject: below --
2023-11-08 22:57 [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.1653314792.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.