summaryrefslogtreecommitdiffstats
path: root/documentation/bsp-guide
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2011-11-10 10:28:25 -0800
committerRichard Purdie <richard.purdie@linuxfoundation.org>2011-11-25 15:24:17 +0000
commit684c35b7aa0898f95ab70a5982ef74ce98107d93 (patch)
tree7c6cb2ead87d121c32ed9d21943a28b54a0bb35d /documentation/bsp-guide
parent8632404294eaa3464797cffc757add6b5d92b7dc (diff)
downloadpoky-684c35b7aa0898f95ab70a5982ef74ce98107d93.tar.gz
documentation: Changed all manual links to point to "latest"
There are many references to YP documentation throughout the YP manual set. They used to have hard-coded links to the current release (e.g. yoctoproject.org/docs/1.1 for Edison). This created a situation where if you went to a document on the website and clicked on a external reference to another manual, you would redirect to the current manual on the website. Really, you would want to go to the latest manual, which is one that is under development. Changing the links to "yoctoproject.org/docs/latest" makes the tip of master, which is used for devloping the next release, always have references to the manuals being developed and not back to the stable released set of manuals. This "latest" and "current" scheme for the links is not perfect. What has to happen when the latest set of the manuals freezes and becomes the next stable release, all the links in the docs will need to be changed from "latest" in the URL to the new release number. So for example, all the "latest" occurences would need to be changed to "1.2". Then for the next cycle as development begins again, the links need to be infused with "latest" again. (From yocto-docs rev: a234aef34303b07671da956de0e94b352797143e) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/bsp-guide')
-rw-r--r--documentation/bsp-guide/bsp-guide.xml2
-rw-r--r--documentation/bsp-guide/bsp.xml10
2 files changed, 6 insertions, 6 deletions
diff --git a/documentation/bsp-guide/bsp-guide.xml b/documentation/bsp-guide/bsp-guide.xml
index 7f06df7110..d5cdd2bd63 100644
--- a/documentation/bsp-guide/bsp-guide.xml
+++ b/documentation/bsp-guide/bsp-guide.xml
@@ -70,7 +70,7 @@
70 <note> 70 <note>
71 Due to production processes, there could be differences between the Yocto Project 71 Due to production processes, there could be differences between the Yocto Project
72 documentation bundled in the release tarball and the 72 documentation bundled in the release tarball and the
73 <ulink url='http://www.yoctoproject.org/docs/1.1/bsp-guide/bsp-guide.html'> 73 <ulink url='http://www.yoctoproject.org/docs/latest/bsp-guide/bsp-guide.html'>
74 Board Support Package (BSP) Developer's Guide</ulink> on 74 Board Support Package (BSP) Developer's Guide</ulink> on
75 the <ulink url='http://www.yoctoproject.org'>Yocto Project</ulink> website. 75 the <ulink url='http://www.yoctoproject.org'>Yocto Project</ulink> website.
76 For the latest version of this manual, see the manual on the website. 76 For the latest version of this manual, see the manual on the website.
diff --git a/documentation/bsp-guide/bsp.xml b/documentation/bsp-guide/bsp.xml
index 8b0d2ab968..329bf87b63 100644
--- a/documentation/bsp-guide/bsp.xml
+++ b/documentation/bsp-guide/bsp.xml
@@ -30,9 +30,9 @@
30 <note> 30 <note>
31 The information here does not provide an example of how to create a BSP. 31 The information here does not provide an example of how to create a BSP.
32 For examples on how to create a BSP, see the 32 For examples on how to create a BSP, see the
33 <ulink url='http://www.yoctoproject.org/docs/1.1/dev-manual/dev-manual.html#dev-manual-bsp-appendix'> 33 <ulink url='http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html#dev-manual-bsp-appendix'>
34 BSP Development Example</ulink> in 34 BSP Development Example</ulink> in
35 <ulink url='http://www.yoctoproject.org/docs/1.1/dev-manual/dev-manual.html'> 35 <ulink url='http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html'>
36 The Yocto Project Development Manual</ulink>. 36 The Yocto Project Development Manual</ulink>.
37 You can also see the 37 You can also see the
38 <ulink url='https://wiki.yoctoproject.org/wiki/Transcript:_creating_one_generic_Atom_BSP_from_another'> 38 <ulink url='https://wiki.yoctoproject.org/wiki/Transcript:_creating_one_generic_Atom_BSP_from_another'>
@@ -100,9 +100,9 @@
100 " 100 "
101 </literallayout> 101 </literallayout>
102 For more detailed information on layers, see the 102 For more detailed information on layers, see the
103 "<ulink url='http://www.yoctoproject.org/docs/1.1/poky-ref-manual/poky-ref-manual.html#usingpoky-changes-layers'>BitBake Layers</ulink>" section of the Yocto Project Reference Manual. 103 "<ulink url='http://www.yoctoproject.org/docs/latest/poky-ref-manual/poky-ref-manual.html#usingpoky-changes-layers'>BitBake Layers</ulink>" section of the Yocto Project Reference Manual.
104 You can also see the detailed examples in the appendices of 104 You can also see the detailed examples in the appendices of
105 <ulink url='http://www.yoctoproject.org/docs/1.1/dev-manual/dev-manual.html'> 105 <ulink url='http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html'>
106 The Yocto Project Development Manual</ulink>. 106 The Yocto Project Development Manual</ulink>.
107 </para> 107 </para>
108 108
@@ -542,7 +542,7 @@
542 The configuration options will likely end up in that location anyway if the BSP gets 542 The configuration options will likely end up in that location anyway if the BSP gets
543 added to the Yocto Project. 543 added to the Yocto Project.
544 For information on how to add these configurations directly, see 544 For information on how to add these configurations directly, see
545 <ulink url='http://yoctoproject.org/docs/1.1/kernel-manual/kernel-manual.html'> 545 <ulink url='http://yoctoproject.org/docs/latest/kernel-manual/kernel-manual.html'>
546 The Yocto Project Kernel Architecture and Use Manual</ulink>.</para> 546 The Yocto Project Kernel Architecture and Use Manual</ulink>.</para>
547 <para> 547 <para>
548 In general, however, the Yocto Project maintainers take care of moving the 548 In general, however, the Yocto Project maintainers take care of moving the