summaryrefslogtreecommitdiffstats
path: root/documentation/kernel-manual/kernel-how-to.xml
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/kernel-manual/kernel-how-to.xml')
-rw-r--r--documentation/kernel-manual/kernel-how-to.xml30
1 files changed, 29 insertions, 1 deletions
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 @@
223 223
224 <para> 224 <para>
225 This section contains several workflow examples. 225 This section contains several workflow examples.
226 Many of the examples use Git commands.
227 You can find Git documentation at
228 <ulink url='http://git-scm.com/documentation'></ulink>.
229 You can find a simple overview of using Git with the Yocto Project in the
230 "<ulink url='http://www.yoctoproject.org/docs/1.1/dev-manual/dev-manual.html#git'>Git</ulink>"
231 section of
232 <ulink url='http://www.yoctoproject.org/docs/1.1/dev-manual/dev-manual.html'>The Yocto
233 Project Development Manual</ulink>.
226 </para> 234 </para>
227 235
228 <section id='change-inspection-kernel-changes-commits'> 236 <section id='change-inspection-kernel-changes-commits'>
@@ -341,6 +349,19 @@
341 </para> 349 </para>
342 350
343 <para> 351 <para>
352 This section and its sub-sections, describe general application of Git's
353 <filename>push</filename> and <filename>pull</filename> commands, which are used to
354 get your changes upstream or source your code from an upstream repository.
355 The Yocto Project provides scripts that help you work in a collaborative development
356 environment.
357 For information on these scripts, see the
358 "<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
359 "<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
360 <ulink url='http://www.yoctoproject.org/docs/1.1/dev-manual/dev-manual.html'>The
361 Yocto Project Development Manual</ulink>".
362 </para>
363
364 <para>
344 There are many ways to save kernel modifications. 365 There are many ways to save kernel modifications.
345 The technique employed 366 The technique employed
346 depends on the destination for the patches: 367 depends on the destination for the patches:
@@ -615,7 +636,14 @@
615 636
616 <para> 637 <para>
617 The messages used to commit changes are a large part of these standards. 638 The messages used to commit changes are a large part of these standards.
618 Consequently, be sure that the headers for each commit have the required information. 639 Consequently, be sure that the headers for each commit have the required information.
640 For information on how to follow the Yocto Project commit message standards, see the
641 "<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
642 <ulink url='http://www.yoctoproject.org/docs/1.1/dev-manual/dev-manual.html'>The
643 Yocto Project Development Manual</ulink>".
644 </para>
645
646 <para>
619 If the initial commits were not properly documented or do not meet those standards, 647 If the initial commits were not properly documented or do not meet those standards,
620 you can re-base by using the <filename>git rebase -i</filename> command to 648 you can re-base by using the <filename>git rebase -i</filename> command to
621 manipulate the commits and 649 manipulate the commits and