documentation/kernel-manual/kernel-how-to.xml: Updated to kernel 3.4
According to Bruce Ashfield, we will be using linux-yocto-3.4. So I changed the linux-yocto-3.0 strings to linux-yocto-3.4. (From yocto-docs rev: 23df0251b04ed7c31ad2297a4a7870861554beef) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
parent
614308eef0
commit
de4cdfd6bc
|
@ -46,9 +46,9 @@
|
||||||
You can find the files used to describe all the valid features and BSPs
|
You can find the files used to describe all the valid features and BSPs
|
||||||
in the Yocto Project kernel in any clone of the Linux Yocto kernel source repository Git tree.
|
in the Yocto Project kernel in any clone of the Linux Yocto kernel source repository Git tree.
|
||||||
For example, the following command clones the Yocto Project baseline kernel that
|
For example, the following command clones the Yocto Project baseline kernel that
|
||||||
branched off of <filename>linux.org</filename> version 3.0:
|
branched off of <filename>linux.org</filename> version 3.4:
|
||||||
<literallayout class='monospaced'>
|
<literallayout class='monospaced'>
|
||||||
$ git clone git://git.yoctoproject.org/linux-yocto-3.0
|
$ git clone git://git.yoctoproject.org/linux-yocto-3.4
|
||||||
</literallayout>
|
</literallayout>
|
||||||
For another example of how to set up a local Git repository of the Linux Yocto
|
For another example of how to set up a local Git repository of the Linux Yocto
|
||||||
kernel files, see the
|
kernel files, see the
|
||||||
|
@ -58,9 +58,9 @@
|
||||||
Once you have cloned the kernel Git repository on your local machine, you can
|
Once you have cloned the kernel Git repository on your local machine, you can
|
||||||
switch to the <filename>meta</filename> branch within the repository.
|
switch to the <filename>meta</filename> branch within the repository.
|
||||||
Here is an example that assumes the local Git repository for the kernel is in
|
Here is an example that assumes the local Git repository for the kernel is in
|
||||||
a top-level directory named <filename>linux-yocto-3.0</filename>:
|
a top-level directory named <filename>linux-yocto-3.4</filename>:
|
||||||
<literallayout class='monospaced'>
|
<literallayout class='monospaced'>
|
||||||
$ cd ~/linux-yocto-3.0
|
$ cd ~/linux-yocto-3.4
|
||||||
$ git checkout -b meta origin/meta
|
$ git checkout -b meta origin/meta
|
||||||
</literallayout>
|
</literallayout>
|
||||||
Once you have checked out and switched to the <filename>meta</filename> branch,
|
Once you have checked out and switched to the <filename>meta</filename> branch,
|
||||||
|
@ -598,9 +598,9 @@
|
||||||
<para>
|
<para>
|
||||||
For example, the following command pushes the changes from your local branch
|
For example, the following command pushes the changes from your local branch
|
||||||
<filename>yocto/standard/common-pc/base</filename> to the remote branch with the same name
|
<filename>yocto/standard/common-pc/base</filename> to the remote branch with the same name
|
||||||
in the master repository <filename>//git.mycompany.com/pub/git/kernel-3.0</filename>.
|
in the master repository <filename>//git.mycompany.com/pub/git/kernel-3.4</filename>.
|
||||||
<literallayout class='monospaced'>
|
<literallayout class='monospaced'>
|
||||||
> git push ssh://git.mycompany.com/pub/git/kernel-3.0 \
|
> git push ssh://git.mycompany.com/pub/git/kernel-3.4 \
|
||||||
yocto/standard/common-pc/base:yocto/standard/common-pc/base
|
yocto/standard/common-pc/base:yocto/standard/common-pc/base
|
||||||
</literallayout>
|
</literallayout>
|
||||||
</para>
|
</para>
|
||||||
|
|
Loading…
Reference in New Issue