slides/yocto-recipe-basics: clarify branch explanation

- Give details about the usefulness of "branch" parameter - Stop mentioning "nobranch=1". Corresponding to a very rare case when SRCREV is not on any branch. Signed-off-by: Michael Opdenacker <[email protected]>
bootlin · Jan 19, 2024 · edcbdb4 · edcbdb4
1 parent 5194bbd
commit edcbdb4
Showing 1 changed file with 4 additions and 2 deletions.
diff --git a/slides/yocto-recipe-basics/yocto-recipe-basics.tex b/slides/yocto-recipe-basics/yocto-recipe-basics.tex
@@ -134,8 +134,10 @@ \subsection{Organization of a recipe}
         \item \code{git://<url>;protocol=<protocol>;branch=<branch>}
         \item When using git, it is necessary to also define
           \yoctovar{SRCREV}. It has to be a commit hash and not a tag to
-          be able to do offline builds. The \code{branch} parameter is
-          mandatory unless \code{nobranch=1} is used.
+          be able to do offline builds (a git tag can change, you then need
+	  to connect to the repository to check for a possible update).
+          The \code{branch} parameter is mandatory as a safety check
+          that \yoctovar{SRCREV} is on the expected branch.
       \end{itemize}
     \item The \code{http}, \code{https} and \code{ftp} schemes:
       \begin{itemize}