diff options
| author | Paul Barker <pbarker@konsulko.com> | 2020-11-27 15:19:08 +0000 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2020-12-03 12:04:21 +0000 |
| commit | 8faafa99cc9a45c1920ec3ea696a9ec7fb653194 (patch) | |
| tree | 0b34a19a12e115e8b63219e5a6aec7a0b58b85bf /documentation/test-manual/test-manual-test-process.rst | |
| parent | 62c061968c12511dc09ad575caa75f8960ac27cf (diff) | |
| download | poky-8faafa99cc9a45c1920ec3ea696a9ec7fb653194.tar.gz | |
documentation: Simplify yocto_wiki links
The `yocto_wiki` external link directive is modified to include the
`/wiki` element of the URL so that we can simplify the links in the
text.
Note that there are still a couple of places where this directive
cannot be used, such as in the table of contents in index.rst.
(From yocto-docs rev: d8aa5f93d349f27db3d03a2c4bcc205649f45a8d)
Signed-off-by: Paul Barker <pbarker@konsulko.com>
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/test-manual/test-manual-test-process.rst')
| -rw-r--r-- | documentation/test-manual/test-manual-test-process.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/documentation/test-manual/test-manual-test-process.rst b/documentation/test-manual/test-manual-test-process.rst index 82b9bb441b..bbf0103803 100644 --- a/documentation/test-manual/test-manual-test-process.rst +++ b/documentation/test-manual/test-manual-test-process.rst | |||
| @@ -25,7 +25,7 @@ at: :yocto_ab:`/typhoon/#/console`. | |||
| 25 | 25 | ||
| 26 | Builds are triggered manually when the test branches are ready. The | 26 | Builds are triggered manually when the test branches are ready. The |
| 27 | builds are monitored by the SWAT team. For additional information, see | 27 | builds are monitored by the SWAT team. For additional information, see |
| 28 | :yocto_wiki:`/wiki/Yocto_Build_Failure_Swat_Team`. | 28 | :yocto_wiki:`/Yocto_Build_Failure_Swat_Team`. |
| 29 | If successful, the changes would usually be merged to the ``master`` | 29 | If successful, the changes would usually be merged to the ``master`` |
| 30 | branch. If not successful, someone would respond to the changes on the | 30 | branch. If not successful, someone would respond to the changes on the |
| 31 | mailing list explaining that there was a failure in testing. The choice | 31 | mailing list explaining that there was a failure in testing. The choice |