summaryrefslogtreecommitdiffstats
path: root/documentation/kernel-manual/kernel-how-to.xml
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/kernel-manual/kernel-how-to.xml
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/kernel-manual/kernel-how-to.xml')
-rw-r--r--documentation/kernel-manual/kernel-how-to.xml22
1 files changed, 11 insertions, 11 deletions
diff --git a/documentation/kernel-manual/kernel-how-to.xml b/documentation/kernel-manual/kernel-how-to.xml
index df8605ed6f..756758d8a3 100644
--- a/documentation/kernel-manual/kernel-how-to.xml
+++ b/documentation/kernel-manual/kernel-how-to.xml
@@ -50,8 +50,8 @@
50 </literallayout> 50 </literallayout>
51 For another example of how to set up a local Git repository of the Linux Yocto 51 For another example of how to set up a local Git repository of the Linux Yocto
52 kernel files, see the 52 kernel files, see the
53 "<ulink url='http://www.yoctoproject.org/docs/1.1/dev-manual/dev-manual.html#local-kernel-files'>Linux Yocto Kernel</ulink>" bulleted item in 53 "<ulink url='http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html#local-kernel-files'>Linux Yocto Kernel</ulink>" bulleted item in
54 <ulink url='http://www.yoctoproject.org/docs/1.1/dev-manual/dev-manual.html'>The Yocto Project Development Manual</ulink>. 54 <ulink url='http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html'>The Yocto Project Development Manual</ulink>.
55 </para> 55 </para>
56 <para> 56 <para>
57 Once the Git repository is set up on your local machine, you can switch to the 57 Once the Git repository is set up on your local machine, you can switch to the
@@ -226,9 +226,9 @@
226 You can find Git documentation at 226 You can find Git documentation at
227 <ulink url='http://git-scm.com/documentation'></ulink>. 227 <ulink url='http://git-scm.com/documentation'></ulink>.
228 You can find a simple overview of using Git with the Yocto Project in the 228 You can find a simple overview of using Git with the Yocto Project in the
229 "<ulink url='http://www.yoctoproject.org/docs/1.1/dev-manual/dev-manual.html#git'>Git</ulink>" 229 "<ulink url='http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html#git'>Git</ulink>"
230 section of 230 section of
231 <ulink url='http://www.yoctoproject.org/docs/1.1/dev-manual/dev-manual.html'>The Yocto 231 <ulink url='http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html'>The Yocto
232 Project Development Manual</ulink>. 232 Project Development Manual</ulink>.
233 </para> 233 </para>
234 234
@@ -354,9 +354,9 @@
354 The Yocto Project provides scripts that help you work in a collaborative development 354 The Yocto Project provides scripts that help you work in a collaborative development
355 environment. 355 environment.
356 For information on these scripts, see the 356 For information on these scripts, see the
357 "<ulink url='http://www.yoctoproject.org/docs/1.1/dev-manual/dev-manual.html#pushing-a-change-upstream'>Pushing a Change Upstream and Requesting a Pull</ulink>" and 357 "<ulink url='http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html#pushing-a-change-upstream'>Pushing a Change Upstream and Requesting a Pull</ulink>" and
358 "<ulink url='http://www.yoctoproject.org/docs/1.1/dev-manual/dev-manual.html#submitting-a-patch'>Submitting a Patch Through Email</ulink>" sections in 358 "<ulink url='http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html#submitting-a-patch'>Submitting a Patch Through Email</ulink>" sections in
359 <ulink url='http://www.yoctoproject.org/docs/1.1/dev-manual/dev-manual.html'>The 359 <ulink url='http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html'>The
360 Yocto Project Development Manual</ulink>". 360 Yocto Project Development Manual</ulink>".
361 </para> 361 </para>
362 362
@@ -637,8 +637,8 @@
637 The messages used to commit changes are a large part of these standards. 637 The messages used to commit changes are a large part of these standards.
638 Consequently, be sure that the headers for each commit have the required information. 638 Consequently, be sure that the headers for each commit have the required information.
639 For information on how to follow the Yocto Project commit message standards, see the 639 For information on how to follow the Yocto Project commit message standards, see the
640 "<ulink url='http://www.yoctoproject.org/docs/1.1/dev-manual/dev-manual.html#how-to-submit-a-change'>How to Submit a Change</ulink>" section in 640 "<ulink url='http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html#how-to-submit-a-change'>How to Submit a Change</ulink>" section in
641 <ulink url='http://www.yoctoproject.org/docs/1.1/dev-manual/dev-manual.html'>The 641 <ulink url='http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html'>The
642 Yocto Project Development Manual</ulink>". 642 Yocto Project Development Manual</ulink>".
643 </para> 643 </para>
644 644
@@ -772,8 +772,8 @@
772 existing similar BSP. 772 existing similar BSP.
773 The information is introductory in nature and does not provide step-by-step examples. 773 The information is introductory in nature and does not provide step-by-step examples.
774 For detailed information on how to create a BSP given an existing similar BSP, see 774 For detailed information on how to create a BSP given an existing similar BSP, see
775 the "<ulink url='http://www.yoctoproject.org/docs/1.1/dev-manual/dev-manual.html#dev-manual-bsp-appendix'>BSP Development Example</ulink>" appendix in 775 the "<ulink url='http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html#dev-manual-bsp-appendix'>BSP Development Example</ulink>" appendix in
776 <ulink url='http://www.yoctoproject.org/docs/1.1/dev-manual/dev-manual.html'>The 776 <ulink url='http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html'>The
777 Yocto Project Development Manual</ulink>, or see the 777 Yocto Project Development Manual</ulink>, or see the
778 <ulink url='https://wiki.yoctoproject.org/wiki/Transcript:_creating_one_generic_Atom_BSP_from_another'>Transcript:_creating_one_generic_Atom_BSP_from_another</ulink> 778 <ulink url='https://wiki.yoctoproject.org/wiki/Transcript:_creating_one_generic_Atom_BSP_from_another'>Transcript:_creating_one_generic_Atom_BSP_from_another</ulink>
779 wiki page. 779 wiki page.