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

documentation/dev-manual/dev-manual-newbie.xml: Edits to Git section 

Last edits to the "Git" section and the bulleted item that defines
the term "Yocto Project Files."  These edits were from a review of
Joshua Lock.

Reported-by: Joshua Lock <joshua.lock@intel.com>
(From yocto-docs rev: 57cbb06aac566e02bb2e2a1ad05c3ff6dbb0359c)

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-02-08 08:29:23 -06:00 committed by Richard Purdie
parent c74f732576
commit 43e6e25bd5
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
documentation/dev-manual/dev-manual-newbie.xml
View File

@ -225,6 +225,7 @@
results in a Yocto Project file structure whose Yocto Project source directory is named
<filename>poky-edison-6.0</filename>.
If you create a Git repository, then you can name the repository anything you like.
By default, your local Git repository is named <filename>poky</filename>.
</para>
<para>
@ -238,7 +239,8 @@
active development repository.
In this case, any local changes you make to the Yocto Project can be later applied to active
development branches of the upstream Yocto Project Git repository.
Furthermore, with the Git repository you can create a local Git branch that
If you want to track a set of local changes while starting from the same point
as a release tarball, you can create a local Git branch that
reflects the exact copy of the files at the time of their release.
You do this using Git tags that are part of the repository.
For more information on concepts, see the section
@ -490,7 +492,7 @@
And, the name of the local branch you have created and checked out is
<filename>edison-6.0</filename>.
The files in your repository now exactly match the Yocto Project 1.1
Release (edison).
Release tag (edison).
It is important to understand that when you create and checkout a local
working branch based on a tag, your environment matches a specific point
in time and not a development branch.