Lines Matching full:changes

146 is usually named "poky", allows you to make changes, contribute to the
239 responsible for accepting changes from other developers and for
254 area. These branches hold changes (commits) to the project that have
257 determines if the changes are qualified to be moved from the "contrib"
263 develop changes. When a developer is satisfied with a particular feature
274 There is a somewhat formal method by which developers commit changes and
278 submitting patches and changes, see the
282 In summary, there is a single point of entry for changes into the
285 develop, test, and submit changes to "contrib" areas for the maintainer
286 to examine. The maintainer then chooses which changes are going to
298 -  *Make Small Changes:* It is best to keep the changes you commit small
299    as compared to bundling many disparate changes into a single commit.
301    maintainer to more easily include or refuse changes.
303 -  *Make Complete Changes:* It is also good practice to leave the
317 -  *Merge Changes:* The ``git merge`` command allows you to take the
318    changes from one branch and fold them into another branch. This
320    be working on different parts of the same feature. Merging changes
328    where the code or change is tested, a "stage" branch where changes
338    pull changes submitted by other developers from the upstream
398 local experimentation on projects as you develop changes or new
402 For example, the Git repository ``poky`` contains all changes and
404 That means that all changes that make up all releases are captured. The
405 repository maintains a complete history of changes.
442 "origin/&DISTRO_NAME_NO_CAP;" branch. Changes you make while in this
456 Git uses "tags" to mark specific changes in a repository branch
498 Git has an extensive set of commands that lets you manage changes and
520    Git uses to track changes. You must stage all files that have changed
523 -  *git commit:* Creates a local "commit" that documents the changes
524    you made. Only changes that have been staged can be committed.
534 -  *git checkout branch-name:* Changes your local working branch and
542    specific features or changes. Using isolated branches facilitates
543    easy removal of changes if they do not work out.
556    which you are basing changes (e.g. the "&DISTRO_NAME_NO_CAP;"
561    all your committed local changes to the upstream Git repository that
564    changes (commits) into the appropriate branch of project's upstream
567 -  *git merge:* Combines or adds changes from one local branch of
571    that you would use for isolated work. You would make your changes in
574    changes from your isolated branch into the currently checked out
581    able to merge all the changes in one branch with another but need to
584 -  *gitk:* Provides a GUI view of the branches and changes in your