From: "Steve Sakoman" <steve@sakoman.com>
To: bitbake-devel@lists.openembedded.org
Subject: [bitbake][dunfell][1.46][PATCH 0/2] Patch review
Date: Mon, 14 Sep 2020 04:19:02 -1000 [thread overview]
Message-ID: <cover.1600092861.git.steve@sakoman.com> (raw)
Please review this set of patches for dunfell and have comments back
by end of day Wednesday.
Tested on dunfell autobuilder builds over the past few weeks.
The following changes since commit 838a89141fd6a75da9f982ad2b035e823b692d2a:
server/process: Account for xmlrpc connections (2020-07-29 00:21:29 +0100)
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
Jean-Francois Dagenais (1):
siggen: clean_basepath: remove recipe full path when virtual:xyz
present
Richard Purdie (1):
fetch2: Drop cups.org from wget status checks
lib/bb/siggen.py | 2 +-
lib/bb/tests/fetch.py | 4 +---
2 files changed, 2 insertions(+), 4 deletions(-)
--
2.17.1
next reply other threads:[~2020-09-14 14:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 14:19 Steve Sakoman [this message]
2020-09-14 14:19 ` [bitbake][dunfell][1.46][PATCH 1/2] siggen: clean_basepath: remove recipe full path when virtual:xyz present Steve Sakoman
2020-09-14 14:19 ` [bitbake][dunfell][1.46][PATCH 2/2] fetch2: Drop cups.org from wget status checks 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
2022-01-13 14:10 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-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.1600092861.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.