summaryrefslogtreecommitdiffstats
path: root/documentation
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2013-04-09 11:16:11 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-04-10 16:20:55 +0100
commitf04dc51f141aa973d870c53594e21784e57b06e1 (patch)
tree2282599b57cfed96657344ef128adb494617b804 /documentation
parentd8f9811fa321a11f93c95d12f4097f351d97d5e6 (diff)
downloadpoky-f04dc51f141aa973d870c53594e21784e57b06e1.tar.gz
dev-manual: Some edits early in Chapter 3.
(From yocto-docs rev: 566af2c28413eeb89b69a59fab087e0145a9493e) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation')
-rw-r--r--documentation/dev-manual/dev-manual-newbie.xml11
1 files changed, 8 insertions, 3 deletions
diff --git a/documentation/dev-manual/dev-manual-newbie.xml b/documentation/dev-manual/dev-manual-newbie.xml
index ce88b3473e..826dcd73f6 100644
--- a/documentation/dev-manual/dev-manual-newbie.xml
+++ b/documentation/dev-manual/dev-manual-newbie.xml
@@ -12,8 +12,10 @@
12 closed, proprietary environment. 12 closed, proprietary environment.
13 Additionally, the Yocto Project uses specific tools and constructs as part of its development 13 Additionally, the Yocto Project uses specific tools and constructs as part of its development
14 environment. 14 environment.
15 This chapter specifically addresses open source philosophy, licensing issues, code repositories, 15 This chapter specifically addresses open source philosophy, using the
16 the open source distributed version control system Git, and best practices using the Yocto Project. 16 Yocto Project in a team environment, source repositories, Yocto Project
17 terms, licensing, the open source distributed version control system Git,
18 workflows, bug tracking, and how to submit changes.
17</para> 19</para>
18 20
19<section id='open-source-philosophy'> 21<section id='open-source-philosophy'>
@@ -66,6 +68,9 @@
66 Thus, you can adapt it to many different use cases and scenarios. 68 Thus, you can adapt it to many different use cases and scenarios.
67 However, these characteristics can cause a struggle if you are trying 69 However, these characteristics can cause a struggle if you are trying
68 to create a working setup that scales across a large team. 70 to create a working setup that scales across a large team.
71 </para>
72
73 <para>
69 To help with these types of situations, this section presents 74 To help with these types of situations, this section presents
70 some of the project's most successful experiences, 75 some of the project's most successful experiences,
71 practices, solutions, and available technologies that work well. 76 practices, solutions, and available technologies that work well.
@@ -110,7 +115,7 @@
110 </para></listitem> 115 </para></listitem>
111 <listitem><para>Keep your cross-development toolchains 116 <listitem><para>Keep your cross-development toolchains
112 updated. 117 updated.
113 You can do this by provisioning either as new 118 You can do this through provisioning either as new
114 toolchain downloads or as updates through a package 119 toolchain downloads or as updates through a package
115 update mechanism using <filename>opkg</filename> 120 update mechanism using <filename>opkg</filename>
116 to provide updates to an existing toolchain. 121 to provide updates to an existing toolchain.