From: Steve Sakoman <steve@sakoman.com>
To: bitbake-devel@lists.openembedded.org
Subject: [bitbake][kirkstone][2.0][PATCH 0/2] Patch review
Date: Wed, 1 Feb 2023 12:19:49 -1000 [thread overview]
Message-ID: <cover.1675289845.git.steve@sakoman.com> (raw)
Please review this set of patches for 2.0/kirkstone and have comments back by
end of day Friday.
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/4872
The following changes since commit ed0dcc40f80c48839bac20298013d70043858a4e:
bb/utils: include SSL certificate paths in export_proxies (2023-01-30 08:37:10 +0000)
are available in the Git repository at:
https://git.openembedded.org/bitbake-contrib stable/2.0-nut
http://cgit.openembedded.org/bitbake-contrib/log/?h=stable/2.0-nut
Marek Vasut (2):
fetch2/git: Prevent git fetcher from fetching gitlab repository
metadata
fetch2/git: Clarify the meaning of namespace
doc/bitbake-user-manual/bitbake-user-manual-fetching.rst | 4 ++--
lib/bb/fetch2/git.py | 9 +++++++--
2 files changed, 9 insertions(+), 4 deletions(-)
--
2.25.1
next reply other threads:[~2023-02-01 22:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 22:19 Steve Sakoman [this message]
2023-02-01 22:19 ` [bitbake][kirkstone][2.0][PATCH 1/2] fetch2/git: Prevent git fetcher from fetching gitlab repository metadata Steve Sakoman
2023-02-01 22:19 ` [bitbake][kirkstone][2.0][PATCH 2/2] fetch2/git: Clarify the meaning of namespace Steve Sakoman
-- strict thread matches above, loose matches on Subject: below --
2022-08-19 20:59 [bitbake][kirkstone][2.0][PATCH 0/2] 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.1675289845.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.