diff --git a/documentation/dev-manual/dev-manual-start.xml b/documentation/dev-manual/dev-manual-start.xml
index 0729baa0da..b0f5e120bd 100644
--- a/documentation/dev-manual/dev-manual-start.xml
+++ b/documentation/dev-manual/dev-manual-start.xml
@@ -79,47 +79,32 @@
them for the supported distributions.
Yocto Project Release:
- You need a release of the Yocto Project.
- You set that up with a local Source Directory
- one of two ways depending on whether you
- are going to contribute back into the Yocto Project or not.
-
- Regardless of the method you use, this manual refers to the resulting local
- hierarchical set of files as the "Source Directory."
+ You need a release of the Yocto Project installed locally on
+ your development system.
+ This local area is referred to as the
+ Source Directory
+ and is created when you use
+ Git to clone a local copy
+ of the upstream poky repository.
+ Working from a copy of the upstream repository allows you
+ to contribute back into the Yocto Project or simply work with
+ the latest software on a development branch.
+ Because Git maintains and creates an upstream repository with
+ a complete history of changes and you are working with a local
+ clone of that repository, you have access to all the Yocto
+ Project development branches and tag names used in the upstream
+ repository.
+ You can view the Yocto Project Source Repositories at
+
-
- Tarball Extraction:
- If you are not going to contribute back into the Yocto
- Project, you can simply go to the
- Yocto Project Website,
- select the "Downloads" tab, and choose what you want.
- Once you have the tarball, just extract it into a
- directory of your choice.
- For example, the following command extracts the
- Yocto Project &DISTRO; release tarball
- into the current working directory and sets up the local Source Directory
- with a top-level folder named &YOCTO_POKY;:
-
- $ tar xfj &YOCTO_POKY_TARBALL;
-
- This method does not produce a local Git repository.
- Instead, you simply end up with a snapshot of the release.
- Git Repository Method: If you are going to be contributing
- back into the Yocto Project or you simply want to keep up
- with the latest developments, you should use Git commands to set up a local
- Git repository of the upstream poky source repository.
- Doing so creates a repository with a complete history of changes and allows
- you to easily submit your changes upstream to the project.
- Because you clone the repository, you have access to all the Yocto Project development
- branches and tag names used in the upstream repository.
- You can view the Yocto Project Source Repositories at
-
- The following transcript shows how to clone the poky
- Git repository into the current working directory.
- The command creates the local repository in a directory named poky.
- For information on Git used within the Yocto Project, see the
- "Git" section.
-
+ The following transcript shows how to clone the
+ poky Git repository into the current
+ working directory.
+ The command creates the local repository in a directory
+ named poky.
+ For information on Git used within the Yocto Project, see
+ the "Git" section.
+
$ git clone git://git.yoctoproject.org/poky
Cloning into 'poky'...
remote: Counting objects: 203728, done.
@@ -127,12 +112,13 @@
remote: Total 203728 (delta 147444), reused 202891 (delta 146614)
Receiving objects: 100% (203728/203728), 95.54 MiB | 308 KiB/s, done.
Resolving deltas: 100% (147444/147444), done.
-
- For another example of how to set up your own local Git repositories, see this
-
- wiki page, which describes how to create both poky
- and meta-intel Git repositories.
-
+
+ For another example of how to set up your own local Git
+ repositories, see this
+
+ wiki page, which describes how to create both
+ poky and meta-intel
+ Git repositories.Yocto Project Kernel:
If you are going to be making modifications to a supported Yocto Project kernel, you
need to establish local copies of the source.