From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: "Mauro Queirós" <maurofrqueiros@gmail.com>,
bitbake-devel@lists.openembedded.org
Subject: Re: [bitbake-devel] [PATCH 1/3] git.py: skip smudging if lfs=0 is set
Date: Fri, 29 May 2020 06:46:13 +0100 [thread overview]
Message-ID: <d373c7f3e2c72c995dbe4af7589f76f3dee9535d.camel@linuxfoundation.org> (raw)
In-Reply-To: <20200528141853.213890-1-maurofrqueiros@gmail.com>
On Thu, 2020-05-28 at 15:18 +0100, Mauro Queirós wrote:
> Git-LFS objects were being fetched even when lfs=0 was not set.
> This patch disables LFS smudging when lfs=0. That way, only the LFS
> pointers
> are downloaded during checkout.
>
> Signed-off-by: Mauro Queiros <maurofrqueiros@gmail.com>
> ---
> lib/bb/fetch2/git.py | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/lib/bb/fetch2/git.py b/lib/bb/fetch2/git.py
> index 5b3793a7..4c7d388e 100644
> --- a/lib/bb/fetch2/git.py
> +++ b/lib/bb/fetch2/git.py
> @@ -475,6 +475,9 @@ class Git(FetchMethod):
>
> need_lfs = ud.parm.get("lfs", "1") == "1"
>
> + if not need_lfs:
> + ud.basecmd = "GIT_LFS_SKIP_SMUDGE=1 " + ud.basecmd
> +
> source_found = False
> source_error = []
Thanks for the patches, the sound good. Unfortunately they cause
bitbake-selftest to fail:
https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/991/steps/8/logs/step1d
Cheers,
Richard
next prev parent reply other threads:[~2020-05-29 5:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 14:18 [PATCH 1/3] git.py: skip smudging if lfs=0 is set Mauro Queirós
2020-05-28 14:18 ` [PATCH 2/3] git.py: LFS bitbake note should not be printed if need_lfs is not set Mauro Queirós
2020-05-28 14:18 ` [PATCH 3/3] git.py: Use the correct branch to check if the repository has LFS objects Mauro Queirós
2020-05-29 5:46 ` Richard Purdie [this message]
2020-05-29 10:12 ` [bitbake-devel] [PATCH 1/3] git.py: skip smudging if lfs=0 is set Mauro Queirós
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=d373c7f3e2c72c995dbe4af7589f76f3dee9535d.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=maurofrqueiros@gmail.com \
/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.