From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <marciohenriques84@gmail.com>, <bitbake-devel@lists.openembedded.org>
Cc: "Marcio Henriques" <marcio.henriques@ctw.bmwgroup.com>
Subject: Re: [bitbake-devel] [PATCH 1/1] bitbake: add BB_GIT_SHALLOW_SKIP_FAST to disable fast shallow mode
Date: Thu, 30 Apr 2026 17:22:42 +0200 [thread overview]
Message-ID: <DI6LC7WABV84.285L0VIK1RR6G@bootlin.com> (raw)
In-Reply-To: <20260430123847.25046-2-marcio.henriques@ctw.bmwgroup.com>
Hi,
On Thu Apr 30, 2026 at 2:38 PM CEST, Marcio Henriques via lists.openembedded.org wrote:
[...]
> diff --git a/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst b/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst
> index 8d8e8b8b..1def16e7 100644
> --- a/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst
> +++ b/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst
> @@ -390,6 +390,25 @@ overview of their function and contents.
> # This defaults to enabled if both BB_GIT_SHALLOW and
> # BB_GENERATE_MIRROR_TARBALLS are enabled
> BB_GENERATE_SHALLOW_TARBALLS ?= "1"
> +
There are some whitespaces here you can remove.
> + :term:`BB_GIT_SHALLOW_SKIP_FAST`
> + When :term:`BB_GIT_SHALLOW` is enabled, BitBake will by default attempt a
> + fast initial shallow clone directly from the upstream repository, bypassing
> + the creation of a local full clone in :term:`DL_DIR`. Setting this variable
> + to ``"1"`` disables that fast path so the fetcher always creates and
> + maintains a local clone in :term:`DL_DIR`, allowing subsequent builds to
> + fetch only the delta of changes rather than re-downloading the full shallow
> + history.
> +
> + This is useful in CI environments where shallow tarballs are treated as
> + fallback artifacts and incremental network efficiency is preferred.
> +
> + Example usage::
> +
> + BB_GIT_SHALLOW ?= "1"
> + BB_GIT_SHALLOW_SKIP_FAST ?= "1"
> +
> + See also :term:`BB_GIT_SHALLOW` and :term:`BB_GIT_SHALLOW_DEPTH`.
This paragraph should be indented with 3 spaces below
:term:`BB_GIT_SHALLOW_SKIP_FAST`.
Antonin
next prev parent reply other threads:[~2026-04-30 15:22 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 ` Antonin Godard [this message]
2026-05-01 9:29 ` [bitbake-devel] " 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
2026-05-12 8:15 ` [bitbake-devel] " 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=DI6LC7WABV84.285L0VIK1RR6G@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=marcio.henriques@ctw.bmwgroup.com \
--cc=marciohenriques84@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.