From: "Steve Sakoman" <steve@sakoman.com>
To: bitbake-devel@lists.openembedded.org
Subject: [bitbake][dunfell][1.46][PATCH 0/4] Patch review
Date: Wed, 3 Feb 2021 04:22:05 -1000 [thread overview]
Message-ID: <cover.1612361853.git.steve@sakoman.com> (raw)
Please review this set of patches for dunfell/1.46 and have comments back by
end of day Friday.
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/1815
The following changes since commit 418c00c570a60845556204b4f52de047b284dd8e:
data_smart: Ensure hash reflects vardepvalue flags correctly (2021-01-26 15:45:01 +0000)
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
Matt Hoosier (1):
fetch/git: download LFS content too during do_fetch
Mauro Queirós (3):
git.py: skip smudging if lfs=0 is set
git.py: LFS bitbake note should not be printed if need_lfs is not set.
git.py: Use the correct branch to check if the repository has LFS
objects.
lib/bb/fetch2/git.py | 56 +++++++++++++++++++++++++++++++++++++++----
lib/bb/tests/fetch.py | 28 +++++++++++++++-------
2 files changed, 72 insertions(+), 12 deletions(-)
--
2.25.1
next reply other threads:[~2021-02-03 14:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 14:22 Steve Sakoman [this message]
2021-02-03 14:22 ` [bitbake][dunfell][1.46][PATCH 1/4] git.py: skip smudging if lfs=0 is set Steve Sakoman
2021-02-03 14:22 ` [bitbake][dunfell][1.46][PATCH 2/4] git.py: LFS bitbake note should not be printed if need_lfs is not set Steve Sakoman
2021-02-03 14:22 ` [bitbake][dunfell][1.46][PATCH 3/4] git.py: Use the correct branch to check if the repository has LFS objects Steve Sakoman
2021-02-03 14:22 ` [bitbake][dunfell][1.46][PATCH 4/4] fetch/git: download LFS content too during do_fetch Steve Sakoman
2021-02-03 15:36 ` [bitbake-devel] [bitbake][dunfell][1.46][PATCH 0/4] Patch review Mikko Rapeli
2021-05-10 14:15 Steve Sakoman
2021-06-15 22:00 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.1612361853.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.