documentation/kernel-manual/kernel-how-to.xml: general edits

Some general edits up to section 3.4.

(From yocto-docs rev: 5bcd22b6372017c4f78b18035193879890ed8244)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2012-01-03 12:04:44 -06:00 committed by Richard Purdie
parent fbfb9b7fd8
commit 40f44ec529
1 changed files with 11 additions and 9 deletions

View File

@ -10,8 +10,8 @@
<title>Introduction</title>
<para>
This chapter describes how to accomplish tasks involving the kernel's tree structure.
This information is designed to help the developer that wants to modify the Yocto Project kernel
and contribute changes upstream to the Yocto Project.
The information is designed to help the developer that wants to modify the Yocto
Project kernel and contribute changes upstream to the Yocto Project.
The information covers the following:
<itemizedlist>
<listitem><para>Tree construction</para></listitem>
@ -24,10 +24,11 @@
<section id='tree-construction'>
<title>Tree Construction</title>
<para>
This section describes construction of the Yocto Project kernel repositories as accomplished
by the Yocto Project team to create kernel repositories, which are found at
<ulink url='http://git.yoctoproject.org/cgit.cgi'>http://git.yoctoproject.org/cgit.cgi</ulink>,
that can be shipped as part of a Yocto Project release.
This section describes construction of the Yocto Project kernel repositories
as accomplished by the Yocto Project team to create kernel repositories.
These kernel repositories are found at
<ulink url='http://git.yoctoproject.org/cgit.cgi'>http://git.yoctoproject.org/cgit.cgi</ulink>
and can be shipped as part of a Yocto Project release.
The team creates these repositories by
compiling and executing the set of feature descriptions for every BSP/feature
in the product.
@ -129,7 +130,8 @@
<ulink url='http://git.yoctoproject.org/cgit.cgi'>http://git.yoctoproject.org/cgit.cgi</ulink>
is the combination of all supported boards and configurations.</para>
<para>The technique the Yocto Project team uses is flexible and allows for seamless
blending of an immutable history with additional deployment specific patches.
blending of an immutable history with additional patches specific to a
deployment.
Any additions to the kernel become an integrated part of the branches.</para>
</note>
</para>
@ -263,9 +265,9 @@
<para>
Following are a few examples that show how to use Git to examine changes.
Note that because the Yocto Project Git repository does not break existing Git
Because the Yocto Project Git repository does not break existing Git
functionality and because there exists many permutations of these types of
commands there are many more methods to discover changes.
commands, there are many more methods to discover changes.
<note>
Unless you provide a commit range
(&lt;kernel-type&gt;..&lt;bsp&gt;-&lt;kernel-type&gt;), <filename>kernel.org</filename> history