summaryrefslogtreecommitdiffstats
path: root/documentation
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2011-09-20 10:01:14 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2011-09-25 17:59:59 +0100
commit15793a82104fd79b5b5c3f1fb84bc455309ab4d6 (patch)
treea2ad1f244671857780afd3bcc1cf8ced70754c0f /documentation
parent5031ba1f3d539052d45cd8aafff2c66ac20a4e3d (diff)
downloadpoky-15793a82104fd79b5b5c3f1fb84bc455309ab4d6.tar.gz
documentation/dev-manual/dev-manual-newbie.xml: note for maintainer
Added a note indicating where you can find the maintainer for yocto code. Suggestion by Robert Berger. (From yocto-docs rev: 8e55cc4c460582964b0267b4f43c14e7100f17fe) 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.xml7
1 files changed, 5 insertions, 2 deletions
diff --git a/documentation/dev-manual/dev-manual-newbie.xml b/documentation/dev-manual/dev-manual-newbie.xml
index b2d801fc2d..eee2b540b1 100644
--- a/documentation/dev-manual/dev-manual-newbie.xml
+++ b/documentation/dev-manual/dev-manual-newbie.xml
@@ -425,11 +425,14 @@
425 The Yocto Project files are maintained using Git in a "master" branch whose Git history 425 The Yocto Project files are maintained using Git in a "master" branch whose Git history
426 tracks every change and whose structure provides branches for all diverging functionality. 426 tracks every change and whose structure provides branches for all diverging functionality.
427 Although there is no need to use Git, many open source projects do so. 427 Although there is no need to use Git, many open source projects do so.
428 For the Yocto Project, a key individual called the "maintainer" is responsible for "master" 428 For the Yocto Project, a key individual called the "maintainer" is responsible for the "master"
429 branch of the Git repository. 429 branch of the Git repository.
430 The "master" branch is the “upstream” repository where the final builds of the project occur. 430 The "master" branch is the “upstream” repository where the final builds of the project occur.
431 The maintainer is responsible for allowing changes in from other developers and for 431 The maintainer is responsible for allowing changes in from other developers and for
432 organizing the underlying branch structure to reflect release strategies and so forth. 432 organizing the underlying branch structure to reflect release strategies and so forth.
433 <note>You can see who is the maintainer for Yocto Project files by examining the
434 <filename>distro_tracking_fields</filename> file in the Yocto Project
435 <filename>meta/conf/distro/include</filename> directory.</note>
433 </para> 436 </para>
434 437
435 <para> 438 <para>