From: Anuj Mittal <anuj.mittal@intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [1.52][PATCH 0/5] Patch review
Date: Mon, 14 Mar 2022 10:13:52 +0800 [thread overview]
Message-ID: <cover.1647223687.git.anuj.mittal@intel.com> (raw)
Please review and merge these changes for 1.52/honister. No issues seen
while testing on autobuilder.
Thanks,
Anuj
The following changes since commit 1428128c787642dca690a7d51f2be793e001ae37:
tests/fetch: Handle upstream master -> main branch change (2022-02-23 18:09:52 +0000)
are available in the Git repository at:
git://push.openembedded.org/bitbake-contrib stable/1.52-next
Daniel Gomez (1):
contrib: Fix hash server Dockerfile dependencies
Daniel Wagenknecht (1):
fetch2: ssh: username and password are optional
Richard Purdie (3):
data_smart: Fix overrides file/line message additions
cooker: Improve parsing failure from handled exception usability
utils: Ensure shell function failure in python logging is correct
contrib/hashserv/Dockerfile | 6 +++++-
lib/bb/cooker.py | 4 +++-
lib/bb/data_smart.py | 8 ++++----
lib/bb/fetch2/ssh.py | 2 +-
lib/bb/utils.py | 2 +-
5 files changed, 14 insertions(+), 8 deletions(-)
--
2.35.1
next reply other threads:[~2022-03-14 2:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 2:13 Anuj Mittal [this message]
2022-03-14 2:13 ` [1.52][PATCH 1/5] contrib: Fix hash server Dockerfile dependencies Anuj Mittal
2022-03-14 2:13 ` [1.52][PATCH 2/5] data_smart: Fix overrides file/line message additions Anuj Mittal
2022-03-14 2:13 ` [1.52][PATCH 3/5] cooker: Improve parsing failure from handled exception usability Anuj Mittal
2022-03-14 2:13 ` [1.52][PATCH 4/5] utils: Ensure shell function failure in python logging is correct Anuj Mittal
2022-03-14 2:13 ` [1.52][PATCH 5/5] fetch2: ssh: username and password are optional 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.1647223687.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.