* [PATCH] [mickledore] ref-manual: add clarification for SRCREV
@ 2023-06-19 13:46 michael.opdenacker
0 siblings, 0 replies; only message in thread
From: michael.opdenacker @ 2023-06-19 13:46 UTC (permalink / raw)
To: docs; +Cc: Michael Opdenacker, Ed Beroset
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
From: Ed Beroset <beroset@ieee.org>
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.
Signed-off-by: Ed Beroset <beroset@ieee.org>
Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
---
documentation/ref-manual/variables.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index 574af2c2f9..d2b83a2cd6 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -7787,7 +7787,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::
--
2.34.1
^ permalink raw reply related [flat|nested] only message in thread
only message in thread, other threads:[~2023-06-19 13:46 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-06-19 13:46 [PATCH] [mickledore] ref-manual: add clarification for SRCREV michael.opdenacker
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox