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>
This commit is contained in:
parent
9786db045f
commit
1017d2aec8
|
@ -425,11 +425,14 @@
|
||||||
The Yocto Project files are maintained using Git in a "master" branch whose Git history
|
The Yocto Project files are maintained using Git in a "master" branch whose Git history
|
||||||
tracks every change and whose structure provides branches for all diverging functionality.
|
tracks every change and whose structure provides branches for all diverging functionality.
|
||||||
Although there is no need to use Git, many open source projects do so.
|
Although there is no need to use Git, many open source projects do so.
|
||||||
For the Yocto Project, a key individual called the "maintainer" is responsible for "master"
|
For the Yocto Project, a key individual called the "maintainer" is responsible for the "master"
|
||||||
branch of the Git repository.
|
branch of the Git repository.
|
||||||
The "master" branch is the “upstream” repository where the final builds of the project occur.
|
The "master" branch is the “upstream” repository where the final builds of the project occur.
|
||||||
The maintainer is responsible for allowing changes in from other developers and for
|
The maintainer is responsible for allowing changes in from other developers and for
|
||||||
organizing the underlying branch structure to reflect release strategies and so forth.
|
organizing the underlying branch structure to reflect release strategies and so forth.
|
||||||
|
<note>You can see who is the maintainer for Yocto Project files by examining the
|
||||||
|
<filename>distro_tracking_fields</filename> file in the Yocto Project
|
||||||
|
<filename>meta/conf/distro/include</filename> directory.</note>
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
|
|
Loading…
Reference in New Issue