From: Steve Sakoman <steve@sakoman.com>
To: bitbake-devel@lists.openembedded.org
Subject: [bitbake][dunfell][1.46][PATCH 0/2] Patch review
Date: Fri, 22 Oct 2021 03:59:13 -1000 [thread overview]
Message-ID: <cover.1634910994.git.steve@sakoman.com> (raw)
Please review this set of patches for dunfell/1.46 and have comments back by
end of day Monday.
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/2787
The following changes since commit 35f01508d687eb44c2dc488cd74a9b35124859d9:
hashserv: let asyncio discover the running loop (2021-10-21 05:57:38 -1000)
are available in the Git repository at:
git://git.openembedded.org/bitbake-contrib stable/1.46-nut
http://cgit.openembedded.org/bitbake-contrib/log/?h=stable/1.46-nut
Richard Purdie (2):
fetch2/git: Avoid races over mirror tarball creation
fetch2/git: Use os.rename instead of mv
lib/bb/fetch2/git.py | 21 +++++++++++++++++++--
1 file changed, 19 insertions(+), 2 deletions(-)
--
2.25.1
next reply other threads:[~2021-10-22 13:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-22 13:59 Steve Sakoman [this message]
2021-10-22 13:59 ` [bitbake][dunfell][1.46][PATCH 1/2] fetch2/git: Avoid races over mirror tarball creation Steve Sakoman
2021-10-22 13:59 ` [bitbake][dunfell][1.46][PATCH 2/2] fetch2/git: Use os.rename instead of mv Steve Sakoman
-- strict thread matches above, loose matches on Subject: below --
2022-11-19 17:51 [bitbake][dunfell][1.46][PATCH 0/2] Patch review Steve Sakoman
2022-03-27 16:43 Steve Sakoman
2022-01-13 14:10 Steve Sakoman
2021-12-03 18:27 Steve Sakoman
2021-11-04 14:11 Steve Sakoman
2021-03-13 19:04 Steve Sakoman
2020-10-12 15:07 Steve Sakoman
2020-09-14 14:19 Steve Sakoman
2020-07-28 22:58 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.1634910994.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