From: michael.opdenacker@bootlin.com
To: docs@lists.yoctoproject.org
Cc: Michael Opdenacker <michael.opdenacker@bootlin.com>
Subject: [PATCH] overview-manual: concepts.rst: fix formating and add references
Date: Fri, 23 Sep 2022 16:43:53 +0200 [thread overview]
Message-ID: <20220923144353.2463680-1-michael.opdenacker@bootlin.com> (raw)
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
---
documentation/overview-manual/concepts.rst | 16 ++++++----------
1 file changed, 6 insertions(+), 10 deletions(-)
diff --git a/documentation/overview-manual/concepts.rst b/documentation/overview-manual/concepts.rst
index 8e0303f0e0..c93f71f8c8 100644
--- a/documentation/overview-manual/concepts.rst
+++ b/documentation/overview-manual/concepts.rst
@@ -703,16 +703,12 @@ the source files and unpack them into the
.. note::
- For every local file (e.g.
- file://
- ) that is part of a recipe's
- SRC_URI
- statement, the OpenEmbedded build system takes a checksum of the file
- for the recipe and inserts the checksum into the signature for the
- do_fetch
- task. If any local file has been modified, the
- do_fetch
- task and all tasks that depend on it are re-executed.
+ For every local file (e.g. ``file://``) that is part of a recipe's
+ :term:`SRC_URI` statement, the OpenEmbedded build system takes a
+ checksum of the file for the recipe and inserts the checksum into
+ the signature for the :ref:`ref-tasks-fetch` task. If any local
+ file has been modified, the :ref:`ref-tasks-fetch` task and all
+ tasks that depend on it are re-executed.
By default, everything is accomplished in the Build Directory, which has
a defined structure. For additional general information on the Build
--
2.34.1
reply other threads:[~2022-09-23 14:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220923144353.2463680-1-michael.opdenacker@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=docs@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox