docs(versioning): add details about commit_id

Signed-off-by: Marco Casaroli <marco.casaroli@gmail.com>

Author: casaroli

docs/BuildSystemLinux.md

@@ -22,6 +22,8 @@ While the file `commit_id.h` includes the commit ID of the Ocre Library.
 If this file is not present in the source tree, the file is generated during the build process and is stored in the build directory.
 If the file does not exist, and the source tree is not a valid git repository, the build will fail.
 
+Check [Versioning](Versioning.md) documentation for more information.
+
 #### Ocre build Configuration
 
 The default Ocre build configuration is in the file `src/platform/posix/include/ocre/platform/config.h`.

docs/BuildSystemZephyr.md

@@ -13,9 +13,9 @@ We provide several points of integration with Zephyr:
 - Ocre West Project
 - Ocre Zephyr Module
 - Ocre Sample Applications
-    - mini
-    - demo
-    - supervisor
+  - mini
+  - demo
+  - supervisor
 
 The general usage of these points of integration are described below.
 
@@ -34,7 +34,7 @@ west init -l .
 
 Here, `-l .` tells west to initialize the project using the manifest (`west.yml` in the current directory).
 
-This will create a `.west` directory in `..` (i.e. side by side with the ocre-runtime directory). And when `west update` is run, Zephyr and its modules will also be checked out in `..`. 
+This will create a `.west` directory in `..` (i.e. side by side with the ocre-runtime directory). And when `west update` is run, Zephyr and its modules will also be checked out in `..`.
 
 This is the recommended way to work with the [Devcontainers](./Devcontainers.md).
 
@@ -88,6 +88,8 @@ If the file does not exist, and the source tree is not a valid git repository, t
 
 Note that these are unrelated to the Zephyr version and the Zephyr application version mechanism (i.e. throught he use of the VERSION file in the Zephyr application directory).
 
+Check [Versioning](Versioning.md) documentation for more information.
+
 #### Kconfig
 
 There are several Kconfig options that can be used to configure Ocre.

docs/Versioning.md

@@ -43,6 +43,13 @@ Generated every time into `commit_id.h` if the source tree is a valid git reposi
 
 The format is `commit-hash[-dirty]`. This is generated by the build system using `git describe --always --abbrev=0 --dirty`, so it means the current commit hash and if there are any uncommitted changes in the working tree (as specificied by the optional `-dirty` suffix).
 
+The `include/ocre/commit_id.h` includes the commit ID of the Ocre Library in Ocre Common library.
+If this file is not present in the source tree, the file is generated during the build process and is stored in the build directory.
+
+If this file does not exist, and the source tree is not a valid git repository, the build will fail.
+
+This file should never be created or modified by the user. When making the source distribution package of Ocre Runtime, this file will be generated in the source directory and the Git metatada will be removed.
+
 ### build_info
 
 The host build information. Generated on every build system by the build system automatically.