1
0
mirror of https://git.yoctoproject.org/poky synced 2026-05-30 00:20:08 +00:00

documentation/dev-manual: Reference link clean-up

I made another pass through the document and cleaned up some
mistakes and also removed redundant links to manuals where I had
already provided a link to the specific section.

(From yocto-docs rev: 5da8ffe100127f5fe4bfd2b478f177d6bef3a968)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark
2012-02-06 12:11:20 -06:00
committed by Richard Purdie
parent 646bda0f1d
commit b97cdc1c8c
4 changed files with 11 additions and 19 deletions
@@ -23,7 +23,7 @@
variables.
For information on variables that are useful for recipes and for information about recipe naming
issues, see the
<ulink url='http://www.yoctoproject.org/docs/latest/poky-ref-manual/poky-ref-manual.html#ref-varlocality-recipe-required'>Required</ulink>" section of the Yocto Project Reference Manual.
"<ulink url='http://www.yoctoproject.org/docs/latest/poky-ref-manual/poky-ref-manual.html#ref-varlocality-recipe-required'>Required</ulink>" section of the Yocto Project Reference Manual.
</para>
<para>
@@ -574,10 +574,8 @@
<para>
For a complete example that shows how to add a new machine to the Yocto Project,
see the
<ulink url='http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html#dev-manual-bsp-appendix'>
BSP Development Example</ulink> in Appendix A of
<ulink url='http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html'>
The Yocto Project Development Manual</ulink>.
"<ulink url='http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html#dev-manual-bsp-appendix'>
BSP Development Example</ulink>" in Appendix A.
</para>
<section id="platdev-newmachine-conffile">
@@ -1015,7 +1013,7 @@
</para>
<para>
The Yocto Project supports a <link linkend='usingpoky-changes-layers'>"layers"</link> concept.
The Yocto Project supports a "<link linkend='usingpoky-changes-layers'>layers</link>" concept.
If you use layers properly, you can ease future upgrades and allow segregation
between the Yocto Project core and a given developer's changes.
The following section provides more advice on managing changes to the Yocto Project.