From: Steve Sakoman <steve@sakoman.com>
To: bitbake-devel@lists.openembedded.org
Subject: [bitbake][dunfell][1.46][PATCH 0/3] Patch review
Date: Tue, 7 Feb 2023 05:09:52 -1000 [thread overview]
Message-ID: <cover.1675782497.git.steve@sakoman.com> (raw)
Please review this set of patches for dunfell/1.46 and have comments back by
end of day Thursday.
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/4893
The following changes since commit c16d364dbf68d2a500fecaf8d6e6d62b11475d9f:
bb/utils: include SSL certificate paths in export_proxies (2023-02-06 23:42:50 +0000)
are available in the Git repository at:
https://git.openembedded.org/bitbake-contrib stable/1.46-nut
http://cgit.openembedded.org/bitbake-contrib/log/?h=stable/1.46-nut
Charlie Davies (1):
bitbake: fetch/git: use shlex.quote() to support spaces in SRC_URI url
Marek Vasut (2):
fetch2/git: Prevent git fetcher from fetching gitlab repository
metadata
fetch2/git: Clarify the meaning of namespace
.../bitbake-user-manual-fetching.rst | 4 ++--
lib/bb/fetch2/git.py | 20 ++++++++++++-------
2 files changed, 15 insertions(+), 9 deletions(-)
--
2.25.1
next reply other threads:[~2023-02-07 15:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 15:09 Steve Sakoman [this message]
2023-02-07 15:09 ` [bitbake][dunfell][1.46][PATCH 1/3] bitbake: fetch/git: use shlex.quote() to support spaces in SRC_URI url Steve Sakoman
2023-02-07 15:09 ` [bitbake][dunfell][1.46][PATCH 2/3] fetch2/git: Prevent git fetcher from fetching gitlab repository metadata Steve Sakoman
2023-02-07 15:09 ` [bitbake][dunfell][1.46][PATCH 3/3] fetch2/git: Clarify the meaning of namespace Steve Sakoman
-- strict thread matches above, loose matches on Subject: below --
2021-11-28 22:02 [bitbake][dunfell][1.46][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.1675782497.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