Lines Matching full:branches

164    -  Be sure to always work in matching branches for both the selected
230 The Yocto Project files are maintained using Git in "branches" whose Git
231 histories track every change and whose structures provide branches for
252 branches in this repository using the web interface of the
254 area. These branches hold changes (commits) to the project that have
258 branches into the "master" branch of the Git repository.
261 maintain cloned repositories of upstream branches. The cloned
309 -  *Use Branches Liberally:* It is very easy to create, use, and delete
310    local branches in your working Git repository on the development
311    host. You can name these branches anything you like. It is helpful to
325 -  *Manage Branches:* Because branches are easy to use, you should use a
326    system where branches indicate varying levels of code readiness. For
330    you can merge code across the branches to reflect ever-increasing
384 Repositories, Tags, and Branches
416 files. Git uses "branches" to organize different development efforts.
417 For example, the ``poky`` repository has several branches that include
419 branches for past Yocto Project releases. You can see all the branches
423 Each of these branches represents a specific area of development. The
425 other branches represent offshoots of the "master" branch.
428 set of branches as the original. This means you can use Git to create a
468 to all the tags in the upstream repository. Similar to branches, you can
541    your work. It is a good idea to use local branches when adding
542    specific features or changes. Using isolated branches facilitates
545 -  *git branch:* Displays the existing local branches associated
584 -  *gitk:* Provides a GUI view of the branches and changes in your