mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-05-09 05:29:32 +00:00
Code Issues Projects Releases Wiki Activity

ref-manual: Changed dev-manual title and fixed links

Browse Source 
Fixed a couple links that were still going to the dev-manual when
they should have been going to the ref-manual.  Updated the title
to the dev-manual for those links.

(From yocto-docs rev: 0cd84696a569af17a12bb939f203051e78d6fd48)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark
2017-10-16 13:18:12 -07:00
committed by Richard Purdie
parent 195d33516a
commit e41c30aa33
1 changed files with 7 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/ref-manual/introduction.xml
+7 -6
View File
@@ -33,7 +33,7 @@
without having to understand concepts, work through the without having to understand concepts, work through the
<ulink url='&YOCTO_DOCS_QS_URL;'>Yocto Project Quick Start</ulink>. <ulink url='&YOCTO_DOCS_QS_URL;'>Yocto Project Quick Start</ulink>.
You can find "how-to" information in the You can find "how-to" information in the
<ulink url='&YOCTO_DOCS_DEV_URL;'>Yocto Project Development Manual</ulink>. <ulink url='&YOCTO_DOCS_DEV_URL;'>Yocto Project Development Tasks Manual</ulink>.
<note><title>Tip</title> <note><title>Tip</title>
For more information about the Yocto Project Documentation set, For more information about the Yocto Project Documentation set,
see the see the
@@ -154,7 +154,8 @@
<ulink url='https://www.yoctoproject.org/organization/enea-ab'>ENEA Linux</ulink> <ulink url='https://www.yoctoproject.org/organization/enea-ab'>ENEA Linux</ulink>
and <ulink url='https://www.yoctoproject.org/ecosystem/member-organizations'>others</ulink>. and <ulink url='https://www.yoctoproject.org/ecosystem/member-organizations'>others</ulink>.
See the "<ulink url='&YOCTO_DOCS_DEV_URL;#creating-your-own-distribution'>Creating Your Own Distribution</ulink>" See the "<ulink url='&YOCTO_DOCS_DEV_URL;#creating-your-own-distribution'>Creating Your Own Distribution</ulink>"
section in the Yocto Project Development Manual for more information. section in the Yocto Project Development Tasks Manual for more
information.
</para> </para>
</section> </section>
@@ -651,12 +652,12 @@
<title>Development Checkouts</title> <title>Development Checkouts</title>
<para> <para>
Development using the Yocto Project requires a local Development using the Yocto Project requires a local
<ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>. <ulink url='&YOCTO_DOCS_REF_URL;#source-directory'>Source Directory</ulink>.
You can set up the Source Directory by cloning a copy of the upstream You can set up the Source Directory by cloning a copy of the upstream
<ulink url='&YOCTO_DOCS_DEV_URL;#poky'>poky</ulink> Git repository. <ulink url='&YOCTO_DOCS_REF_URL;#poky'>poky</ulink> Git repository.
For information on how to do this, see the For information on how to do this, see the
"<ulink url='&YOCTO_DOCS_DEV_URL;#working-with-yocto-project-source-files'>Working With Yocto Project Source Files</ulink>" "<ulink url='&YOCTO_DOCS_DEV_URL;#working-with-yocto-project-source-files'>Working With Yocto Project Source Files</ulink>"
section in the Yocto Project Development Manual. section in the Yocto Project Development Tasks Manual.
</para> </para>
</section> </section>
@@ -687,7 +688,7 @@
information in the similarly-named recipe file. information in the similarly-named recipe file.
For an example of an append file in use, see the For an example of an append file in use, see the
"<ulink url='&YOCTO_DOCS_DEV_URL;#using-bbappend-files'>Using .bbappend Files in Your Layer</ulink>" "<ulink url='&YOCTO_DOCS_DEV_URL;#using-bbappend-files'>Using .bbappend Files in Your Layer</ulink>"
section in the Yocto Project Development Manual. section in the Yocto Project Development Tasks Manual.
<note> <note>
Append files can also use wildcard patterns in their Append files can also use wildcard patterns in their
version numbers so they can be applied to more than one version numbers so they can be applied to more than one