Skip to contentSkip to conversation

fetch2/git: Clarify the meaning of namespace

PATCH New Marek Vasut 1 participant 1 message Dec 18, 2022

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 fetch2/git: Clarify the meaning of namespace

Namespace in this context means a branch, a tag, etc., clarify it in the description. Also, fix a typo "a any", replace with plain "any".

This patch is based of feedback on new applied patch
d32e5b0e ("fetch2/git: Prevent git fetcher from fetching gitlab repository metadata")

---
Cc: Alexandre Belloni <[email protected]>
Cc: Joshua Watt <[email protected]>
Cc: Peter Kjellerstedt <[email protected]>
Cc: Quentin Schulz <[email protected]>
Cc: Richard Purdie <[email protected]>

---
 doc/bitbake-user-manual/bitbake-user-manual-fetching.rst | 4 ++--
 lib/bb/fetch2/git.py                                     | 3 ++-
 2 files changed, 4 insertions(+), 3 deletions(-)
doc/bitbake-user-manual/bitbake-user-manual-fetching.rst +2 -2
index bd117190..c061bd70 100644
@@ -424,8 +424,8 @@ This fetcher supports the following parameters:
 
 -  *"nobranch":* Tells the fetcher to not check the SHA validation for
    the branch when set to "1". The default is "0". Set this option for
-   the recipe that refers to the commit that is valid for a any namespace
-   instead of the branch.
+   the recipe that refers to the commit that is valid for any namespace
+   (branch, tag, ...) instead of the branch.
 
 -  *"bareclone":* Tells the fetcher to clone a bare clone into the
    destination directory without checking out a working tree. Only the
lib/bb/fetch2/git.py +2 -1
index c80e8e5c..2e3d3251 100644
@@ -44,7 +44,8 @@ Supported SRC_URI options are:
 
 - nobranch
    Don't check the SHA validation for branch. set this option for the recipe
-   referring to commit which is valid in any namespace instead of branch.
+   referring to commit which is valid in any namespace (branch, tag, ...)
+   instead of branch.
    The default is "0", set nobranch=1 if needed.
 
 - usehead
Signature · 1 line
2.35.1