From: "Anuj Mittal" <anuj.mittal@intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [1.50][PATCH 0/5] review request
Date: Mon, 26 Apr 2021 11:27:47 +0800 [thread overview]
Message-ID: <cover.1619407547.git.anuj.mittal@intel.com> (raw)
Please review these changes for hardknott/1.50.
Thanks,
Anuj
The following changes since commit b32e6c8d4ea2f83fe77021207e9db883fec82d97:
bitbake-user-manual: add REQUIRED_VERSION and adjust PREFERRED_VERSION entry (2021-04-15 15:01:47 +0100)
are available in the Git repository at:
git://push.openembedded.org/bitbake-contrib stable/1.50-next
Mikko Rapeli (2):
bitbake: tests/fetch: fix test execution without .gitconfig
bitbake: tests/fetch: remove write protected files too
Niels Avonds (1):
fetch/gitsm: Fix crash when using git LFS and submodules
Richard Purdie (1):
runqueue: Fix deferred task issues
Ross Burton (1):
bitbake-server: ensure server timeout is a float
bin/bitbake-server | 2 +-
lib/bb/fetch2/git.py | 2 +-
lib/bb/runqueue.py | 4 ++++
lib/bb/server/process.py | 2 +-
lib/bb/tests/fetch.py | 20 ++++++++++++++++++--
5 files changed, 25 insertions(+), 5 deletions(-)
--
2.30.2
next reply other threads:[~2021-04-26 3:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 3:27 Anuj Mittal [this message]
2021-04-26 3:27 ` [1.50][PATCH 1/5] runqueue: Fix deferred task issues Anuj Mittal
2021-04-27 16:57 ` [bitbake-devel] " Mark Hatle
2021-04-28 1:30 ` Anuj Mittal
2021-04-26 3:27 ` [1.50][PATCH 2/5] bitbake: tests/fetch: fix test execution without .gitconfig Anuj Mittal
2021-04-26 3:27 ` [1.50][PATCH 3/5] bitbake: tests/fetch: remove write protected files too Anuj Mittal
2021-04-26 3:27 ` [1.50][PATCH 4/5] bitbake-server: ensure server timeout is a float Anuj Mittal
2021-04-26 3:27 ` [1.50][PATCH 5/5] fetch/gitsm: Fix crash when using git LFS and submodules Anuj Mittal
-- strict thread matches above, loose matches on Subject: below --
2021-09-15 23:19 [1.50][PATCH 0/5] Review request Anuj Mittal
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.1619407547.git.anuj.mittal@intel.com \
--to=anuj.mittal@intel.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.