From ab06a2e244dacb02afc9de3d2bc8aa0bf8ee3269 Mon Sep 17 00:00:00 2001 From: Ed Beroset Date: Wed, 7 Jun 2023 09:58:31 -0400 Subject: Add clarification for SRCREV It was not clear to me what a "full revision identifier" was in the context of the note documenting SRCREV. After clarification via IRC, this submission attempts to clarify what is meant to help future readers. (From yocto-docs rev: 484a2d039ffbdde4229cbe20f0ab2c5fc8217d88) Signed-off-by: Ed Beroset Reviewed-by: Michael Opdenacker Signed-off-by: Richard Purdie --- documentation/ref-manual/variables.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'documentation') diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst index 6a7888ab47..5b96e4efe3 100644 --- a/documentation/ref-manual/variables.rst +++ b/documentation/ref-manual/variables.rst @@ -7942,7 +7942,7 @@ system and gives an overview of their function and contents. that if you want to build a fixed revision and you want to avoid performing a query on the remote repository every time BitBake parses your recipe, you should specify a :term:`SRCREV` that is a full revision - identifier and not just a tag. + identifier (e.g. the full SHA hash in git) and not just a tag. .. note:: -- cgit v1.2.3-54-g00ecf