sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

kernel-dev: Edits in the Branch section. 

simple edits.

(From yocto-docs rev: 3f73e53c9bdbe71f04400aedc042f19a48ea62bb)

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 2013-01-10 08:48:27 -08:00 committed by Richard Purdie
parent 7eccfa6849
commit b663741f7f
1 changed files with 55 additions and 60 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
documentation/kernel-dev/kernel-dev-advanced.xml
View File

@ -1377,21 +1377,6 @@ the KTYPE has changed, now set to "tiny".
<title>Working with Branches</title>
<para>
We need a top-level section here that introduces branches in general.
There is information that can be pulled from the embedded machine
and feature sections to introduce this stuff.
The two subsections should deal with each type of specific branch
that can be used.
</para>
<section id='machine-branches'>
<title>Machine Branches</title>
<para>
The "<link linkend='using-kernel-metadata-in-a-recipe'>Using Kernel Metadata in a Recipe</link>"
section introduced the <filename>KBRANCH</filename> variable, which
defines the source branch to use from the Linux kernel Git repository
you are using.
Many linux-yocto-custom derived recipes will be using Linux kernel
sources with only a single branch: "master".
However, when you are working with multiple boards and architectures,
@ -1449,6 +1434,16 @@ the KTYPE has changed, now set to "tiny".
additional complexity of branching in your Linux kernel sources.
</para>
<section id='machine-branches'>
<title>Machine Branches</title>
<para>
The "<link linkend='using-kernel-metadata-in-a-recipe'>Using Kernel Metadata in a Recipe</link>"
section introduced the <filename>KBRANCH</filename> variable, which
defines the source branch to use from the Linux kernel Git repository
you are using.
</para>
<para>
If you are supporting multiple boards and architectures and find
yourself with numerous branches, you might consider using a