From: Scott Rifenbark Date: Mon, 27 Aug 2018 18:22:44 +0000 (-0700) Subject: dev-manual: Updates to "Cloning and Checking Out Branches" X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=ed84cafb037e27f2ebd777b424174808ad7c9265;p=thirdparty%2Fopenembedded%2Fopenembedded-core-contrib.git dev-manual: Updates to "Cloning and Checking Out Branches" Provided clearer text. (From yocto-docs rev: 16b793389b359ee08b632d77c1d0abad4796543a) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- diff --git a/documentation/dev-manual/dev-manual-start.xml b/documentation/dev-manual/dev-manual-start.xml index af04528a7b0..12694da89b8 100644 --- a/documentation/dev-manual/dev-manual-start.xml +++ b/documentation/dev-manual/dev-manual-start.xml @@ -901,23 +901,19 @@ Cloning and Checking Out Branches - To use the Yocto Project, you need a release of the Yocto Project - locally installed on your development system. - The locally installed set of files is referred to as the + To use the Yocto Project for development, you need a release locally + installed on your development system. + This locally installed set of files is referred to as the Source Directory in the Yocto Project documentation. - You create your Source Directory by using + The preferred method of creating your Source Directory is by using Git to clone a local copy of the upstream poky repository. - Tip - The preferred method of getting the Yocto Project Source - Directory set up is to clone the repository. - - Working from a copy of the upstream repository allows you - to contribute back into the Yocto Project or simply work with + Working from a cloned copy of the upstream repository allows you + to contribute back into the Yocto Project or to 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