The "Repositories, Tags, and Branches" section had some wording
that described how branches are maintained in the poky repo that
made it hard to maintain in the doc from release to release. I had
a list of past releases by name and as such would have to update
it every release to make it reflect the last set. Well... this
is not the best way to do this and proved out as it slipped through
the cracks for the YP 1.8 release. Consequently, I recast the text
so it is "release proof".
(From yocto-docs rev:
b6e27d06df58a43bb767e9616ccf3c0711e83cf6)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
not files.
Git uses "branches" to organize different development efforts.
For example, the <filename>poky</filename> repository has
- <filename>denzil</filename>, <filename>danny</filename>,
- <filename>dylan</filename>, <filename>dora</filename>,
- <filename>daisy</filename>, and <filename>master</filename> branches
- among others.
+ several branches that include the current
+ <filename>&DISTRO_NAME;</filename> branch, the
+ <filename>master</filename> branch, and many branches for past
+ Yocto Project releases.
You can see all the branches by going to
<ulink url='&YOCTO_GIT_URL;/cgit.cgi/poky/'></ulink> and
clicking on the