All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: bitbake-devel@lists.openembedded.org, kergoth@gmail.com,
	Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: andre.draszik@linaro.org
Subject: Re: [bitbake-devel] [PATCH 0/2] fetch2/git: Use git shallow fetch to implement clone_shallow_local()
Date: Thu, 27 Jun 2024 13:46:03 +0800	[thread overview]
Message-ID: <179dfa77-f266-40d7-b0d4-5ea86bd0f2e3@windriver.com> (raw)
In-Reply-To: <cover.1718886475.git.liezhi.yang@windriver.com>

Hi RP and Christopher,

On 6/20/24 20:44, Robert Yang via lists.openembedded.org wrote:
> From: Robert Yang <liezhi.yang@windriver.com>
> 
> * Test info
>    bitbake-selftest works well
>    bitbake world works well with the shallow tarballs

Do you have any comments on the patches, please?

// Robert

> 
> // Robert
> 
> The following changes since commit 5d88faa0f35f0205c1475893d8589d1e6533dcc0:
> 
>    bitbake: siggen: catch FileNotFoundError everywhere and ConnectionError also in get_unihashes (2024-06-18 08:45:22 +0100)
> 
> are available in the Git repository at:
> 
>    https://github.com/robertlinux/yocto rbt/shallow
>    https://github.com/robertlinux/yocto/tree/rbt/shallow
> 
> Robert Yang (2):
>    fetch2/git: Use git shallow fetch to implement clone_shallow_local()
>    bitbake: tests/fetch: Update GitShallowTest for clone_shallow_local()
> 
>   bitbake/lib/bb/fetch2/git.py  | 71 ++++++++++++++++++++++-------------
>   bitbake/lib/bb/tests/fetch.py | 13 ++++---
>   2 files changed, 53 insertions(+), 31 deletions(-)
> 
> 
> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#16368): https://lists.openembedded.org/g/bitbake-devel/message/16368
> Mute This Topic: https://lists.openembedded.org/mt/106779045/7304958
> Group Owner: bitbake-devel+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/bitbake-devel/unsub [liezhi.yang@eng.windriver.com]
> -=-=-=-=-=-=-=-=-=-=-=-
> 


  parent reply	other threads:[~2024-06-27  5:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-20 12:44 [PATCH 0/2] fetch2/git: Use git shallow fetch to implement clone_shallow_local() liezhi.yang
2024-06-20 12:44 ` [PATCH 1/2] " liezhi.yang
2024-06-20 12:44 ` [PATCH 2/2] bitbake: tests/fetch: Update GitShallowTest for clone_shallow_local() liezhi.yang
2024-06-27  5:46 ` Robert Yang [this message]
2024-07-01 22:13 ` [bitbake-devel] [PATCH 0/2] fetch2/git: Use git shallow fetch to implement clone_shallow_local() Alexandre Belloni
2024-07-02  7:31   ` Robert Yang
2024-07-07  7:11     ` Robert Yang

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=179dfa77-f266-40d7-b0d4-5ea86bd0f2e3@windriver.com \
    --to=liezhi.yang@windriver.com \
    --cc=andre.draszik@linaro.org \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=kergoth@gmail.com \
    --cc=richard.purdie@linuxfoundation.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.