summaryrefslogtreecommitdiffstats
path: root/documentation/dev-manual/dev-manual-newbie.xml
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/dev-manual/dev-manual-newbie.xml')
-rw-r--r--documentation/dev-manual/dev-manual-newbie.xml12
1 files changed, 6 insertions, 6 deletions
diff --git a/documentation/dev-manual/dev-manual-newbie.xml b/documentation/dev-manual/dev-manual-newbie.xml
index e09c373da2..65e17e24a0 100644
--- a/documentation/dev-manual/dev-manual-newbie.xml
+++ b/documentation/dev-manual/dev-manual-newbie.xml
@@ -97,7 +97,7 @@
97 <para> 97 <para>
98 Most teams have many pieces of software undergoing active development at any given time. 98 Most teams have many pieces of software undergoing active development at any given time.
99 You can derive large benefits by putting these pieces under the control of a source 99 You can derive large benefits by putting these pieces under the control of a source
100 control system that is compatible (i.e. Git or Subversion (SVN)) with the OpenEmbeded 100 control system that is compatible (i.e. Git or Subversion (SVN)) with the OpenEmbedded
101 build system that the Yocto Project uses. 101 build system that the Yocto Project uses.
102 You can then set the autobuilder to pull the latest revisions of the packages 102 You can then set the autobuilder to pull the latest revisions of the packages
103 and test the latest commits by the builds. 103 and test the latest commits by the builds.
@@ -131,7 +131,7 @@
131 <listitem><para>Maintain your metadata in layers that make sense 131 <listitem><para>Maintain your metadata in layers that make sense
132 for your situation. 132 for your situation.
133 See the "<link linkend='understanding-and-creating-layers'>Understanding 133 See the "<link linkend='understanding-and-creating-layers'>Understanding
134 and Creating Layeres</link>" section for more information on 134 and Creating Layers</link>" section for more information on
135 layers.</para></listitem> 135 layers.</para></listitem>
136 <listitem><para>Separate the project's metadata and code by using 136 <listitem><para>Separate the project's metadata and code by using
137 separate Git repositories. 137 separate Git repositories.
@@ -187,7 +187,7 @@
187 </para> 187 </para>
188 188
189 <para> 189 <para>
190 Once you are set up through either tarball extraction or creation of Git repositories, 190 Once you are set up through either tarball extraction or a checkout of Git repositories,
191 you are ready to develop. 191 you are ready to develop.
192 </para> 192 </para>
193 193
@@ -362,7 +362,7 @@
362 In its most general sense, it is an open-source project that was initially developed 362 In its most general sense, it is an open-source project that was initially developed
363 by OpenedHand. With OpenedHand, poky was developed off of the existing OpenEmbedded 363 by OpenedHand. With OpenedHand, poky was developed off of the existing OpenEmbedded
364 build system becoming a build system for embedded images. 364 build system becoming a build system for embedded images.
365 After Intel Corporation aquired OpenedHand, the project poky became the basis for 365 After Intel Corporation acquired OpenedHand, the project poky became the basis for
366 the Yocto Project's build system. 366 the Yocto Project's build system.
367 Within the Yocto Project source repositories, poky exists as a separate Git repository 367 Within the Yocto Project source repositories, poky exists as a separate Git repository
368 that can be cloned to yield a local copy on the host system. 368 that can be cloned to yield a local copy on the host system.
@@ -380,7 +380,7 @@
380 and unpacking a Yocto Project release tarball or creating a local copy of 380 and unpacking a Yocto Project release tarball or creating a local copy of
381 the <filename>poky</filename> Git repository 381 the <filename>poky</filename> Git repository
382 <filename>git://git.yoctoproject.org/poky</filename>. 382 <filename>git://git.yoctoproject.org/poky</filename>.
383 Sometimes you might here the term "poky directory" used to refer to this 383 Sometimes you might hear the term "poky directory" used to refer to this
384 directory structure. 384 directory structure.
385 <note> 385 <note>
386 The OpenEmbedded build system does not support file or directory names that 386 The OpenEmbedded build system does not support file or directory names that
@@ -422,7 +422,7 @@
422 reflects the exact copy of the files at the time of their release. 422 reflects the exact copy of the files at the time of their release.
423 You do this by using Git tags that are part of the repository.</para> 423 You do this by using Git tags that are part of the repository.</para>
424 424
425 <para>For more information on concepts around Git repositories, branches, and tags, 425 <para>For more information on concepts related to Git repositories, branches, and tags,
426 see the 426 see the
427 "<link linkend='repositories-tags-and-branches'>Repositories, Tags, and Branches</link>" 427 "<link linkend='repositories-tags-and-branches'>Repositories, Tags, and Branches</link>"
428 section.</para></listitem> 428 section.</para></listitem>