From: "Marcio Henriques" <marciohenriques84@gmail.com>
To: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH 1/1] bitbake: add BB_GIT_SHALLOW_SKIP_FAST to disable fast shallow mode
Date: Mon, 11 May 2026 09:14:02 -0700 [thread overview]
Message-ID: <1495889.1778516042086994585@lists.openembedded.org> (raw)
In-Reply-To: <7ac8312de40809f14006bfff65143f002543c50b.camel@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 866 bytes --]
On Tue, May 5, 2026 at 10:41 AM, Richard Purdie wrote:
>
> FWIW the git fetcher is specifically coded to avoid removing
> references. It shouldn't remove old revisions or obsolete heads (e.g.
> for repos that changed master -> main). If it is doing that, that is
> something we should fix.
This is also about dealing with force pushes that may remove something that
was previously merged and is no longer available in DL_DIR/git2 or upstream.
>
> I can see why you might decide to do that but it will be a pretty
> inefficient use of space with an archive for every revision and means
> turning everything into shallow clones, which has its own challenges.
It can actually also be more efficient as the git fetcher fetches all branches and this may
require more space than just archiving the source code for the revisions used in the build.
[-- Attachment #2: Type: text/html, Size: 1017 bytes --]
next prev parent reply other threads:[~2026-05-11 16:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 12:38 [PATCH 0/1] Subject: [RFC PATCH] bitbake: fetch2/git: add switch to disable fast shallow path Marcio Henriques
2026-04-30 12:38 ` [PATCH 1/1] bitbake: add BB_GIT_SHALLOW_SKIP_FAST to disable fast shallow mode Marcio Henriques
2026-04-30 15:22 ` [bitbake-devel] " Antonin Godard
2026-05-01 9:29 ` Richard Purdie
2026-05-05 8:08 ` Marcio Henriques
2026-05-05 9:41 ` [bitbake-devel] " Richard Purdie
2026-05-11 16:14 ` Marcio Henriques [this message]
2026-05-12 8:15 ` Richard Purdie
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=1495889.1778516042086994585@lists.openembedded.org \
--to=marciohenriques84@gmail.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.