Lines Matching full:upstream
162 to create a local copy of the upstream repositories.
181 For steps on how to view and access these upstream Git repositories,
237 repository. The development branch is the "upstream" repository from which
250 The Yocto Project ``poky`` Git repository also has an upstream
261 maintain cloned repositories of upstream branches. The cloned
268 with whatever upstream branch they are working against. They are also
276 maintainer include them into an upstream branch. This process is called
338 pull changes submitted by other developers from the upstream
346 ":ref:`dev-manual/common-tasks:using scripts to push a change upstream and request a pull`"
430 development branch from the upstream source Git repository. In other
440 local copy of the upstream ``poky`` Git repository and checks out a
441 local branch named "&DISTRO_NAME_NO_CAP;", which tracks the upstream
443 branch would ultimately affect the upstream "&DISTRO_NAME_NO_CAP;" branch
450 "master" branch of the upstream repository. In other words, creating and
468 to all the tags in the upstream repository. Similar to branches, you can
484 command makes all the upstream tags available locally in your
486 a branch named "my-rocko-18.0.0" that is based on the upstream branch
489 particular Yocto Project release as it is tagged in the upstream Git
516 equal footing with a fellow developer's Git repository or an upstream
528 upstream repository.
532 commits as compared to the upstream repository.
538 - *git checkout -b working-branch upstream-branch:* Creates and
540 tracks the upstream branch. You can use your local branch to isolate
553 - *git pull \-\-rebase*: Retrieves information from an upstream Git
560 - *git push repo-name local-branch:upstream-branch:* Sends
561 all your committed local changes to the upstream Git repository that
564 changes (commits) into the appropriate branch of project's upstream
596 them upstream or not.
621 follow the upstream licensing scheme. You can find information on the