diff options
| author | Scott Rifenbark <srifenbark@gmail.com> | 2017-10-16 15:08:29 -0700 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2017-10-30 15:55:06 +0000 |
| commit | e42ddecaf0b18ea2872be86025f377841fb719bf (patch) | |
| tree | b1362902d0f76110532429e07c8ced187796d5de /documentation | |
| parent | 65e3cb65b27cb4c3584f3959ca7a8f55c314fb75 (diff) | |
| download | poky-e42ddecaf0b18ea2872be86025f377841fb719bf.tar.gz | |
ref-manual: Converted external links to internal and fixed dev-manual links
The dev-manual title changed to the Yocto Project Development Tasks
Manual and I fixed those links. Converted links that should have
been internal to the ref-manual but were external to the dev-manual.
(From yocto-docs rev: 6de68b04ce1b921466a462dfa3f3485232aaf40d)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation')
| -rw-r--r-- | documentation/ref-manual/ref-release-process.xml | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/documentation/ref-manual/ref-release-process.xml b/documentation/ref-manual/ref-release-process.xml index f8fc49c191..e2902eb38b 100644 --- a/documentation/ref-manual/ref-release-process.xml +++ b/documentation/ref-manual/ref-release-process.xml | |||
| @@ -61,9 +61,9 @@ | |||
| 61 | <para> | 61 | <para> |
| 62 | Each major release receives a codename that identifies the release in | 62 | Each major release receives a codename that identifies the release in |
| 63 | the | 63 | the |
| 64 | <ulink url='&YOCTO_DOCS_REF_URL;#yocto-project-repositories'>Yocto Project Source Repositories</ulink>. | 64 | <link linkend='yocto-project-repositories'>Yocto Project Source Repositories</link>. |
| 65 | The concept is that branches of | 65 | The concept is that branches of |
| 66 | <ulink url='&YOCTO_DOCS_REF_URL;#metadata'>Metadata</ulink> | 66 | <link linkend='metadata'>Metadata</link> |
| 67 | with the same codename are likely to be compatible and thus | 67 | with the same codename are likely to be compatible and thus |
| 68 | work together. | 68 | work together. |
| 69 | <note> | 69 | <note> |
| @@ -131,7 +131,7 @@ | |||
| 131 | Yocto Project. | 131 | Yocto Project. |
| 132 | For information on how to run available tests on your projects, see the | 132 | For information on how to run available tests on your projects, see the |
| 133 | "<ulink url='&YOCTO_DOCS_DEV_URL;#performing-automated-runtime-testing'>Performing Automated Runtime Testing</ulink>" | 133 | "<ulink url='&YOCTO_DOCS_DEV_URL;#performing-automated-runtime-testing'>Performing Automated Runtime Testing</ulink>" |
| 134 | section in the Yocto Project Development Manual. | 134 | section in the Yocto Project Development Tasks Manual. |
| 135 | </para> | 135 | </para> |
| 136 | 136 | ||
| 137 | <para> | 137 | <para> |
| @@ -217,7 +217,7 @@ | |||
| 217 | in the <filename>poky</filename> repository. | 217 | in the <filename>poky</filename> repository. |
| 218 | <note> | 218 | <note> |
| 219 | You can find all these branches in the Yocto Project | 219 | You can find all these branches in the Yocto Project |
| 220 | <ulink url='&YOCTO_DOCS_REF_URL;#source-repositories'>Source Repositories</ulink>. | 220 | <link linkend='source-repositories'>Source Repositories</link>. |
| 221 | </note> | 221 | </note> |
| 222 | Testing within these public branches ensures in a publicly visible way | 222 | Testing within these public branches ensures in a publicly visible way |
| 223 | that all of the main supposed architectures and recipes in OE-Core | 223 | that all of the main supposed architectures and recipes in OE-Core |