Re: [bitbake-devel] [PATCH 1/1] bitbake: add BB_GIT_SHALLOW_SKIP_FAST to disable fast shallow mode
"Antonin Godard" <[email protected]>
| Newsgroups | org.openembedded.lists.bitbake-devel |
|---|---|
| Message-ID | <[email protected]> |
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