summaryrefslogtreecommitdiffstats
path: root/documentation/overview-manual/development-environment.rst
diff options
context:
space:
mode:
authorQuentin Schulz <quentin.schulz@cherry.de>2025-06-18 17:13:35 +0200
committerRichard Purdie <richard.purdie@linuxfoundation.org>2025-06-20 09:48:15 +0100
commitbebe66feaee45e1e280a63e089bd894bc9227ee5 (patch)
tree3cc194e3b6a9816099c92ceeace02d1d152683b1 /documentation/overview-manual/development-environment.rst
parent931db3845c12129322c07b007f2e7831a304d231 (diff)
downloadpoky-bebe66feaee45e1e280a63e089bd894bc9227ee5.tar.gz
tree-wide: make the :doc: directive use absolute paths
This makes all :doc: directives use an absolute paths (with the root directory being documentation/ in the repo). This is then consistent across the whole source and is easier to review and move files around, you just need to know where a file is located relative to documentation/ directory and use that. This gets rid of paths looking in parent directory with '..' as well as expecting a file to be in the same directory as the other file it points to via the :doc: directive. (From yocto-docs rev: b9457f2005b0bea49c54e9727eb30e9458084886) Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/overview-manual/development-environment.rst')
-rw-r--r--documentation/overview-manual/development-environment.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/documentation/overview-manual/development-environment.rst b/documentation/overview-manual/development-environment.rst
index d79173ff55..066d784314 100644
--- a/documentation/overview-manual/development-environment.rst
+++ b/documentation/overview-manual/development-environment.rst
@@ -240,7 +240,7 @@ and so forth.
240 240
241 For information on finding out who is responsible for (maintains) a 241 For information on finding out who is responsible for (maintains) a
242 particular area of code in the Yocto Project, see the 242 particular area of code in the Yocto Project, see the
243 ":doc:`../contributor-guide/identify-component`" 243 ":doc:`/contributor-guide/identify-component`"
244 section of the Yocto Project and OpenEmbedded Contributor Guide. 244 section of the Yocto Project and OpenEmbedded Contributor Guide.
245 245
246The Yocto Project ``poky`` Git repository also has an upstream 246The Yocto Project ``poky`` Git repository also has an upstream
@@ -272,7 +272,7 @@ push them into the "contrib" area and subsequently request that the
272maintainer include them into an upstream branch. This process is called 272maintainer include them into an upstream branch. This process is called
273"submitting a patch" or "submitting a change." For information on 273"submitting a patch" or "submitting a change." For information on
274submitting patches and changes, see the 274submitting patches and changes, see the
275":doc:`../contributor-guide/submit-changes`" section in the Yocto Project 275":doc:`/contributor-guide/submit-changes`" section in the Yocto Project
276and OpenEmbedded Contributor Guide. 276and OpenEmbedded Contributor Guide.
277 277
278In summary, there is a single point of entry for changes into the 278In summary, there is a single point of entry for changes into the
@@ -347,7 +347,7 @@ Book <https://book.git-scm.com>`__.
347 this type of change, you format the patch and then send the email 347 this type of change, you format the patch and then send the email
348 using the Git commands ``git format-patch`` and ``git send-email``. 348 using the Git commands ``git format-patch`` and ``git send-email``.
349 For information on how to use these scripts, see the 349 For information on how to use these scripts, see the
350 ":doc:`../contributor-guide/submit-changes`" section in the Yocto Project 350 ":doc:`/contributor-guide/submit-changes`" section in the Yocto Project
351 and OpenEmbedded Contributor Guide. 351 and OpenEmbedded Contributor Guide.
352 352
353Git 353Git