It's really painful to clone large size repository (such as Linux kernel) under bad network condition. It should allow git clone use --depth parameter to reduce data size. Most of the time, we don't need too long history. I didn't find any parameter can do this in the document. If no such feature, I suggest to add this option.
This isn't quite as simple as you'd imagine. Shallow clones make mirroring harder, some servers refuse to do shallow clones from arbitrary SHAs, and incremental updates become trickier. However, what you're looking for is implemented, albeit at a global level instead of per-recipe: https://docs.yoctoproject.org/bitbake/dev/bitbake-user-manual/bitbake-user-manual-ref-variables.html#term-BB_GIT_SHALLOW
(In reply to Ross Burton from comment #1) > This isn't quite as simple as you'd imagine. Shallow clones make mirroring > harder, some servers refuse to do shallow clones from arbitrary SHAs, and > incremental updates become trickier. > > However, what you're looking for is implemented, albeit at a global level > instead of per-recipe: > https://docs.yoctoproject.org/bitbake/dev/bitbake-user-manual/bitbake-user- > manual-ref-variables.html#term-BB_GIT_SHALLOW Thank you very much for the document.