Home
last modified time | relevance | path

Searched refs:shallow (Results 1 – 19 of 19) sorted by relevance

/openbmc/openbmc/poky/bitbake/lib/bblayers/
H A Dlayerindex.py29 def get_fetch_layer(self, fetchdir, url, subdir, fetch_layer, branch, shallow=False): argument
38 if shallow:
214 args.shallow)
242 args.shallow = True
/openbmc/openbmc/poky/bitbake/lib/bb/fetch2/
H A Dgitannex.py24 if ud.shallow:
49 if not ud.shallow or ud.localpath != ud.fullshallow:
H A Dgit.py200 ud.shallow = d.getVar("BB_GIT_SHALLOW") == "1"
238 if ud.shallow and not ud.shallow_revs and ud.shallow_depths[ud.name] == 0:
240 ud.shallow = False
282 if ud.shallow:
320 if ud.shallow and ud.write_shallow_tarballs and self.clonedir_need_shallow_revs(ud, d):
346 return ud.shallow and ud.write_shallow_tarballs and not os.path.exists(ud.fullshallow)
355 if ud.shallow and not os.path.exists(origud.fullshallow):
383 if ud.shallow and os.path.exists(ud.fullshallow) and self.need_update(ud, d):
445 if ud.shallow and not ud.shallow_skip_fast:
486 if ud.shallow and ud.write_shallow_tarballs:
[all …]
H A Dgitsm.py155 if ud.shallow and os.path.exists(ud.fullshallow) and unpack:
233 if ud.shallow:
/openbmc/openbmc/poky/bitbake/doc/bitbake-user-manual/
H A Dbitbake-user-manual-ref-variables.rst301 "1" causes bitbake to generate shallow mirror tarballs when fetching git
302 repositories. The number of commits included in the shallow mirror
306 enabled, bitbake will generate shallow mirror tarballs by default for git
307 repositories. This separate variable exists so that shallow tarball
315 …generating mirror tarballs of `shallow git repositories <https://riptutorial.com/git/example/4584/…
316 … The external `git-make-shallow <https://git.openembedded.org/bitbake/tree/bin/git-make-shallow>`_
317 script is used for shallow mirror tarball creation.
319 When :term:`BB_GIT_SHALLOW` is enabled, bitbake will attempt to fetch a shallow
320 mirror tarball. If the shallow mirror tarball cannot be fetched, it will
323 This setting causes an initial shallow clone instead of an initial full bare clone.
[all …]
/openbmc/openbmc/poky/scripts/
H A Dcreate-pull-request192 git format-patch $extraopts -M40 --subject-prefix="$PREFIX" -n -o $ODIR --thread=shallow --cover-le…
/openbmc/openbmc/poky/meta/classes-global/
H A Dmirrors.bbclass70 # Switch llvm, glibc and binutils recipes to use shallow clones as they're large and this
/openbmc/openbmc/poky/documentation/migration-guides/
H A Drelease-notes-4.0.25.rst42 - bitbake: tests/fetch: Fix git shallow test failure with git >= 2.48
H A Drelease-notes-5.1.3.rst35 - bitbake: tests/fetch: Fix git shallow test failure with git >= 2.48
H A Drelease-notes-4.3.3.rst44 - dtc: preserve version also from shallow git clones
H A Drelease-notes-5.0.7.rst169 - bitbake: tests/fetch: Fix git shallow test failure with git >= 2.48
H A Drelease-notes-4.0.6.rst110 - mirrors.bbclass: use shallow tarball for binutils-native
H A Drelease-notes-4.1.1.rst110 - mirrors.bbclass: use shallow tarball for binutils-native
H A Drelease-notes-5.2.rst347 - Add support for fast initial shallow fetch. The fetcher will prefer an
348 initial shallow clone, but will re-utilize an existing bare clone if
349 there is one. If the remote server does not allow shallow fetches, the
H A Drelease-notes-5.0.rst222 - ``git-make-shallow`` script: add support for Git's ``safe.bareRepository=explicit``
H A Drelease-notes-4.0.rst203 - glibc and binutils recipes now use shallow mirror tarballs for faster fetching
H A Drelease-notes-4.2.rst328 …- :ref:`ref-classes-mirrors` class: use shallow tarball for ``binutils-native``/``nativesdk-binut…
/openbmc/qemu/docs/devel/
H A Dsubmitting-a-patch.rst356 letter, with shallow threading (all patches in the series are
/openbmc/qemu/docs/interop/
H A Dlive-block-operations.rst678 Sometimes, this is also referred to as "shallow copy" -- because only