From afde290655c47bbd20bedcbc971fcf59302ecd83 Mon Sep 17 00:00:00 2001 From: Nicolas Dechesne Date: Tue, 28 Apr 2020 23:36:21 +0200 Subject: sphinx: overview-manual: add figures The automatic conversion with pandoc skipped the figures. Add them manually. (From yocto-docs rev: 1c2d071b7963490e8126a0b81792bda7a7c0bc8c) Signed-off-by: Nicolas Dechesne Signed-off-by: Richard Purdie --- .../overview-manual-development-environment.rst | 12 ++++++++++++ 1 file changed, 12 insertions(+) (limited to 'documentation/overview-manual/overview-manual-development-environment.rst') diff --git a/documentation/overview-manual/overview-manual-development-environment.rst b/documentation/overview-manual/overview-manual-development-environment.rst index 4e6770c4f4..abd775be84 100644 --- a/documentation/overview-manual/overview-manual-development-environment.rst +++ b/documentation/overview-manual/overview-manual-development-environment.rst @@ -179,6 +179,9 @@ development: Yocto Metadata Layers. You can create local copies of Git repositories for each of these areas. + .. image:: figures/source-repos.png + :align: center + For steps on how to view and access these upstream Git repositories, see the "`Accessing Source Repositories <&YOCTO_DOCS_DEV_URL;#accessing-source-repositories>`__" @@ -191,6 +194,9 @@ development: these files does not produce a local copy of the Git repository but rather a snapshot of a particular release or image. + .. image:: figures/index-downloads.png + :align: center + For steps on how to view and access these files, see the "`Accessing Index of Releases <&YOCTO_DOCS_DEV_URL;#accessing-index-of-releases>`__" @@ -205,6 +211,9 @@ development: form. The tarballs are similar to those found in the `Index of /releases: <&YOCTO_DL_URL;/releases/>`__ area. + .. image:: figures/yp-download.png + :align: center + For steps on how to use the "DOWNLOADS" page, see the "`Using the Downloads Page <&YOCTO_DOCS_DEV_URL;#using-the-downloads-page>`__" section in the Yocto Project Development Tasks Manual. @@ -285,6 +294,9 @@ develop, test, and submit changes to "contrib" areas for the maintainer to examine. The maintainer then chooses which changes are going to become a permanent part of the project. +.. image:: figures/git-workflow.png + :align: center + While each development environment is unique, there are some best practices or methods that help development run smoothly. The following list describes some of these practices. For more information about Git -- cgit v1.2.3-54-g00ecf