dev-manual: Fixed broken links to "Source Directory" term.

Fixes [YOCTO #11630]

Moving the "Yocto Project Terms" section from dev-manual to
ref-manual broke all the links to the "Source Directory" term.
I fixed them.

(From yocto-docs rev: d3a206b141e0b0c623362622ec73bbf44118071a)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

1 files changed, 9 insertions, 9 deletions

diff --git a/documentation/dev-manual/dev-manual-newbie.xml b/documentation/dev-manual/dev-manual-newbie.xml
index b9fc265211..b64036af61 100644
--- a/documentation/dev-manual/dev-manual-newbie.xml
+++ b/documentation/dev-manual/dev-manual-newbie.xml
@@ -418,7 +418,7 @@
         column and see the URL at the bottom of the page that you need to clone
         a Git repository for that particular item.
         Having a local Git repository of the
-        <link linkend='source-directory'>Source Directory</link>, which is
+        <ulink url='&YOCTO_DOCS_REF_URL;#source-directory'>Source Directory</ulink>, which is
         usually named "poky", allows
         you to make changes, contribute to the history, and ultimately enhance
         the Yocto Project's tools, Board Support Packages, and so forth.
@@ -435,7 +435,7 @@
             <itemizedlist>
                 <listitem><para>
                     The recommended method for setting up the Yocto Project
-                    <link linkend='source-directory'>Source Directory</link>
+                    <ulink url='&YOCTO_DOCS_REF_URL;#source-directory'>Source Directory</ulink>
                     and the files for supported BSPs
                     (e.g., <filename>meta-intel</filename>) is to use
                     <link linkend='git'>Git</link> to create a local copy of
@@ -444,7 +444,7 @@
                 <listitem><para>
                     Be sure to always work in matching branches for both
                     the selected BSP repository and the
-                    <link linkend='source-directory'>Source Directory</link>
+                    <ulink url='&YOCTO_DOCS_REF_URL;#source-directory'>Source Directory</ulink>
                     (i.e. <filename>poky</filename>) repository.
                     For example, if you have checked out the "master" branch
                     of <filename>poky</filename> and you are going to use
@@ -522,7 +522,7 @@
         When you build an image using the Yocto Project, the build process uses a
         known list of licenses to ensure compliance.
         You can find this list in the
-        <link linkend='source-directory'>Source Directory</link> at
+        <ulink url='&YOCTO_DOCS_REF_URL;#source-directory'>Source Directory</ulink> at
         <filename>meta/files/common-licenses</filename>.
         Once the build completes, the list of all licenses found and used during that build are
         kept in the
@@ -554,7 +554,7 @@
         You can find a list of the combined SPDX and OSI licenses that the
         Yocto Project uses in the
         <filename>meta/files/common-licenses</filename> directory in your
-        <link linkend='source-directory'>Source Directory</link>.
+        <ulink url='&YOCTO_DOCS_REF_URL;#source-directory'>Source Directory</ulink>.
     </para>
 
     <para>
@@ -665,7 +665,7 @@
      $ git checkout -b &DISTRO_NAME_NO_CAP; origin/&DISTRO_NAME_NO_CAP;
             </literallayout>
             In this example, the name of the top-level directory of your local
-            <link linkend='source-directory'>Source Directory</link>
+            <ulink url='&YOCTO_DOCS_REF_URL;#source-directory'>Source Directory</ulink>
             is "poky" and the name of that local working area (local branch)
             you just created and checked out is "&DISTRO_NAME_NO_CAP;".
             The files in your local repository now reflect the same files that
@@ -960,7 +960,7 @@
                 workflow.
                 You can find these scripts in the <filename>scripts</filename>
                 folder of the
-                <link linkend='source-directory'>Source Directory</link>.
+                <ulink url='&YOCTO_DOCS_REF_URL;#source-directory'>Source Directory</ulink>.
                 For information on how to use these scripts, see the
                 "<link linkend='pushing-a-change-upstream'>Using Scripts to Push a Change Upstream and Request a Pull</link>" section.
                 </para></listitem>
@@ -1216,7 +1216,7 @@
                     <emphasis>Maintenance File:</emphasis>
                     Examine the <filename>maintainers.inc</filename> file, which is
                     located in the
-                    <link linkend='source-directory'>Source Directory</link>
+                    <ulink url='&YOCTO_DOCS_REF_URL;#source-directory'>Source Directory</ulink>
                     at <filename>meta-poky/conf/distro/include</filename>, to
                     see who is responsible for code.
                     </para></listitem>
@@ -1371,7 +1371,7 @@
                     These scripts are <filename>create-pull-request</filename> and
                     <filename>send-pull-request</filename>.
                     You can find these scripts in the <filename>scripts</filename> directory
-                    within the <link linkend='source-directory'>Source Directory</link>.</para>
+                    within the <ulink url='&YOCTO_DOCS_REF_URL;#source-directory'>Source Directory</ulink>.</para>
                     <para>Using these scripts correctly formats the requests without introducing any
                     whitespace or HTML formatting.
                     The maintainer that receives your patches needs to be able to save and apply them