From: michael.opdenacker@bootlin.com
To: docs@lists.yoctoproject.org
Cc: Michael Opdenacker <michael.opdenacker@bootlin.com>
Subject: [PATCH] ref-manual: simplify internal references
Date: Wed, 1 Mar 2023 15:02:49 +0100 [thread overview]
Message-ID: <20230301140249.394381-1-michael.opdenacker@bootlin.com> (raw)
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
Use a target when available or a direct reference
to a section in the same document.
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
---
documentation/ref-manual/devtool-reference.rst | 6 +++---
documentation/ref-manual/release-process.rst | 2 +-
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/documentation/ref-manual/devtool-reference.rst b/documentation/ref-manual/devtool-reference.rst
index 32e64d02a2..8e62c21425 100644
--- a/documentation/ref-manual/devtool-reference.rst
+++ b/documentation/ref-manual/devtool-reference.rst
@@ -189,7 +189,7 @@ external source tree.
run your application. If dependent packages (e.g. libraries) do not
exist on the target, your application, when run, will fail to find
those functions. For more information, see the
- ":ref:`ref-manual/devtool-reference:deploying your software on the target machine`"
+ ":ref:`devtool-deploying-your-software-on-the-target-machine`"
section.
By default, ``devtool add`` uses the latest revision (i.e. master) when
@@ -555,7 +555,7 @@ Removing Your Software from the Target Machine
Use the ``devtool undeploy-target`` command to remove deployed build
output from the target machine. For the ``devtool undeploy-target``
command to work, you must have previously used the
-":ref:`devtool deploy-target <ref-manual/devtool-reference:deploying your software on the target machine>`"
+":ref:`devtool deploy-target <devtool-deploying-your-software-on-the-target-machine>`"
command::
$ devtool undeploy-target recipe target
@@ -599,7 +599,7 @@ The ``devtool status`` command has no command-line options::
$ devtool status
Following is sample output after using
-:ref:`devtool add <ref-manual/devtool-reference:adding a new recipe to the workspace layer>`
+:ref:`devtool add <devtool-adding-a-new-recipe-to-the-workspace>`
to create and add the ``mtr_0.86.bb`` recipe to the ``workspace`` directory::
$ devtool status
diff --git a/documentation/ref-manual/release-process.rst b/documentation/ref-manual/release-process.rst
index 19e8040638..085d56a608 100644
--- a/documentation/ref-manual/release-process.rst
+++ b/documentation/ref-manual/release-process.rst
@@ -15,7 +15,7 @@ Major and Minor Release Cadence
The Yocto Project delivers major releases (e.g. &DISTRO;) using a six
month cadence roughly timed each April and October of the year.
Following are examples of some major YP releases with their codenames
-also shown. See the ":ref:`ref-manual/release-process:major release codenames`"
+also shown. See the "`Major Release Codenames`_"
section for information on codenames used with major releases.
- 2.2 (Morty)
--
2.37.2
reply other threads:[~2023-03-01 14:02 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=20230301140249.394381-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