From: Steve Sakoman <steve@sakoman.com>
To: bitbake-devel@lists.openembedded.org
Subject: [bitbake][kirkstone][2.0][PATCH 00/14] Pull request (cover letter only)
Date: Fri, 16 Sep 2022 06:54:14 -1000 [thread overview]
Message-ID: <cover.1663347153.git.steve@sakoman.com> (raw)
The following changes since commit ce9fe70156e8f909a3a81da017b89ea61bc6fe38:
utils: Pass lock argument in fileslocked (2022-09-02 11:44:47 +0100)
are available in the Git repository at:
git://git.openembedded.org/bitbake-contrib stable/2.0-next
http://cgit.openembedded.org/bitbake-contrib/log/?h=stable/2.0-next
Gennaro Iorio (1):
fetch2: gitsm: fix incorrect handling of git submodule relative urls
Jacob Kroon (1):
bitbake-user-manual: Correct description of the ??= operator
Jose Quaresma (3):
bitbake: bitbake-user-manual: hashserv can be accessed on a dedicated
domain
bb/utils: remove: check the path again the expand python glob
bb/utils: movefile: use the logger for printing
Michael Opdenacker (3):
doc: bitbake-user-manual: add explicit target for crates fetcher
doc: bitbake-user-manual: document npm and npmsw fetchers
bitbake-user-manual: npm fetcher: improve description of SRC_URI
format
Mikko Rapeli (1):
event.py: ignore exceptions from stdout and sterr operations in atexit
Ola x Nilsson (1):
ConfHandler: Remove lingering close
Richard Purdie (4):
runqueue: Fix unihash cache mismatch issues
cooker: Drop sre_constants usage
ConfHandler/BBHandler: Improve comment error messages and add tests
fetch2: Ensure directory exists before creating symlink
.../bitbake-user-manual-fetching.rst | 78 ++++++++++++++++++-
.../bitbake-user-manual-metadata.rst | 55 +++++++++----
.../bitbake-user-manual-ref-variables.rst | 2 +-
lib/bb/cooker.py | 5 +-
lib/bb/event.py | 10 ++-
lib/bb/fetch2/__init__.py | 2 +
lib/bb/fetch2/gitsm.py | 2 +-
lib/bb/parse/parse_py/BBHandler.py | 4 +-
lib/bb/parse/parse_py/ConfHandler.py | 11 ++-
lib/bb/runqueue.py | 3 +
lib/bb/tests/parse.py | 23 ++++++
lib/bb/utils.py | 16 ++--
12 files changed, 172 insertions(+), 39 deletions(-)
--
2.25.1
reply other threads:[~2022-09-16 16:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.1663347153.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.