summaryrefslogtreecommitdiffstats
path: root/documentation/dev-manual/dev-manual-newbie.xml
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2013-04-09 11:27:10 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-04-10 16:20:56 +0100
commitb7b64ae73fdcf741d0d0fa6cb06d999975ae02c2 (patch)
treea13c92780641a23315d83ef4e830b71f353081d1 /documentation/dev-manual/dev-manual-newbie.xml
parentf09cca6d49a03e3057cc15e61837c5b0b7308eea (diff)
downloadpoky-b7b64ae73fdcf741d0d0fa6cb06d999975ae02c2.tar.gz
dev-manual: Edits to "Policies and Change Flow" section.
(From yocto-docs rev: 9d4c4fdaec73a0bba3e19872cad24a8c2463da58) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/dev-manual/dev-manual-newbie.xml')
-rw-r--r--documentation/dev-manual/dev-manual-newbie.xml4
1 files changed, 2 insertions, 2 deletions
diff --git a/documentation/dev-manual/dev-manual-newbie.xml b/documentation/dev-manual/dev-manual-newbie.xml
index 759871a2b3..2f6805625b 100644
--- a/documentation/dev-manual/dev-manual-newbie.xml
+++ b/documentation/dev-manual/dev-manual-newbie.xml
@@ -316,14 +316,14 @@
316 <title>Policies and Change Flow</title> 316 <title>Policies and Change Flow</title>
317 317
318 <para> 318 <para>
319 The Yocto Project itself uses a hierarchy structure and a 319 The Yocto Project itself uses a hierarchical structure and a
320 pull model. 320 pull model.
321 Scripts exist to create and send pull requests 321 Scripts exist to create and send pull requests
322 (i.e. <filename>create-pull-request</filename> and 322 (i.e. <filename>create-pull-request</filename> and
323 <filename>send-pull-request</filename>). 323 <filename>send-pull-request</filename>).
324 This model is in line with other open source projects where 324 This model is in line with other open source projects where
325 maintainers are responsible for specific areas of the project 325 maintainers are responsible for specific areas of the project
326 and a single maintainer handles the final top-of-tree merges. 326 and a single maintainer handles the final "top-of-tree" merges.
327 </para> 327 </para>
328 328
329 <note> 329 <note>