From 0e623482d5fffb06dc887a1cb5aa87f924a3d3b3 Mon Sep 17 00:00:00 2001
From: Scott Rifenbark <scott.m.rifenbark@intel.com>
Date: Thu, 29 Sep 2011 11:05:07 -0700
Subject: documentation/kernel-manual: Added some references to other areas of
 YP docs.

(From yocto-docs rev: 20754cb376e65b7262b754afad839e0c2b82d7f7)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
 documentation/kernel-manual/kernel-how-to.xml | 30 ++++++++++++++++++++++++++-
 1 file changed, 29 insertions(+), 1 deletion(-)

(limited to 'documentation/kernel-manual/kernel-how-to.xml')

diff --git a/documentation/kernel-manual/kernel-how-to.xml b/documentation/kernel-manual/kernel-how-to.xml
index e62cfad655..259e8200d7 100644
--- a/documentation/kernel-manual/kernel-how-to.xml
+++ b/documentation/kernel-manual/kernel-how-to.xml
@@ -223,6 +223,14 @@
 
         <para>
             This section contains several workflow examples.
+            Many of the examples use Git commands. 
+            You can find Git documentation at 
+            <ulink url='http://git-scm.com/documentation'></ulink>.
+            You can find a simple overview of using Git with the Yocto Project in the 
+            "<ulink url='http://www.yoctoproject.org/docs/1.1/dev-manual/dev-manual.html#git'>Git</ulink>"
+            section of  
+            <ulink url='http://www.yoctoproject.org/docs/1.1/dev-manual/dev-manual.html'>The Yocto 
+            Project Development Manual</ulink>.
         </para>
 
         <section id='change-inspection-kernel-changes-commits'>
@@ -340,6 +348,19 @@
                 This method also provides many tools to commit, undo and export those modifications.
             </para>
 
+            <para>
+                This section and its sub-sections, describe general application of Git's 
+                <filename>push</filename> and <filename>pull</filename> commands, which are used to 
+                get your changes upstream or source your code from an upstream repository.  
+                The Yocto Project provides scripts that help you work in a collaborative development 
+                environment.  
+                For information on these scripts, see the
+                "<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   
+                "<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    
+                <ulink url='http://www.yoctoproject.org/docs/1.1/dev-manual/dev-manual.html'>The 
+                Yocto Project Development Manual</ulink>".
+            </para>
+
             <para>
                 There are many ways to save kernel modifications.
                 The technique employed
@@ -615,7 +636,14 @@
 
                 <para>
                     The messages used to commit changes are a large part of these standards.
-                    Consequently, be sure that the headers for each commit have the required information. 
+                    Consequently, be sure that the headers for each commit have the required information.
+                    For information on how to follow the Yocto Project commit message standards, see the
+                    "<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  
+                    <ulink url='http://www.yoctoproject.org/docs/1.1/dev-manual/dev-manual.html'>The 
+                    Yocto Project Development Manual</ulink>".
+                </para>
+
+                <para>
                     If the initial commits were not properly documented or do not meet those standards,
                     you can re-base by using the <filename>git rebase -i</filename> command to 
                     manipulate the commits and
-- 
cgit v1.2.3-54-g00ecf