Lines Matching full:git
14 repositories, workflows, Git, and licensing.
143 see the URL at the bottom of the page that you need to clone a Git
144 repository for that particular item. Having a local Git repository of
161 :ref:`overview-manual/development-environment:git`
175 Yocto Metadata Layers. You can create local copies of Git
181 For steps on how to view and access these upstream Git repositories,
189 these files does not produce a local copy of the Git repository but
214 Git Workflows and the Yocto Project
218 :ref:`overview-manual/development-environment:git`.
219 Git is a free, open source distributed version control
221 section provides workflow concepts using the Yocto Project and Git. In
230 The Yocto Project files are maintained using Git in "branches" whose Git
232 all diverging functionality. Although there is no need to use Git, many
236 responsible for the integrity of the development branch of a given Git
250 The Yocto Project ``poky`` Git repository also has an upstream
251 contribution Git repository named ``poky-contrib``. You can see all the
258 branches into the "master" branch of the Git repository.
283 development branch of the Git repository, which is controlled by the
289 .. image:: svg/git-workflow.*
294 list describes some of these practices. For more information about Git
295 workflows, see the workflow topics in the `Git Community
296 Book <https://book.git-scm.com>`__.
310 local branches in your working Git repository on the development
317 - *Merge Changes:* The ``git merge`` command allows you to take the
351 considered for the development branch of the Git repository. To send
353 using the Git commands ``git format-patch`` and ``git send-email``.
358 Git chapter
361 The Yocto Project makes extensive use of Git, which is a free, open
362 source distributed version control system. Git supports distributed
364 is best that you have some fundamental understanding of how Git tracks
365 projects and how to work with Git if you are going to use the Yocto
367 Git works and provides you with a summary of some essential Git
372 - For more information on Git, see
373 https://git-scm.com/documentation.
375 - If you need to download Git, it is recommended that you add Git to
377 Ubuntu, use the Ubuntu Software feature). For the Git download
378 page, see https://git-scm.com/download.
388 ":ref:`overview-manual/development-environment:git workflows and the yocto project`"
391 Git repository.
393 Git repositories use branching techniques that track content change (not
401 A Git repository represents all development efforts for a given project.
402 For example, the Git repository ``poky`` contains all changes and
408 ``git clone`` command. When you clone a Git repository, you end up with
411 locally. For examples on how to clone Git repositories, see the
415 It is important to understand that Git tracks content change and not
416 files. Git uses "branches" to organize different development efforts.
427 When you create a local copy of a Git repository, the copy has the same
428 set of branches as the original. This means you can use Git to create a
430 development branch from the upstream source Git repository. In other
431 words, you can define your local Git environment to work on any
433 following example Git commands::
436 $ git clone git://git.yoctoproject.org/poky -b &DISTRO_NAME_NO_CAP;
439 after moving to the home directory, the ``git clone`` command creates a
440 local copy of the upstream ``poky`` Git repository and checks out a
456 Git uses "tags" to mark specific changes in a repository branch
459 tags used with the ``poky`` Git repository by going to :yocto_git:`/poky/`
467 When you create a local copy of the Git repository, you also have access
469 create and checkout a local working Git branch based on a tag name. When
470 you do this, you get a snapshot of the Git repository that reflects the
476 $ git clone git://git.yoctoproject.org/poky
478 $ git fetch --tags
479 $ git checkout tags/rocko-18.0.0 -b my_rocko-18.0.0
483 ``poky``. After moving to the ``poky`` directory, the ``git fetch``
485 repository. Finally, the ``git checkout`` command creates and checks out
489 particular Yocto Project release as it is tagged in the upstream Git
498 Git has an extensive set of commands that lets you manage changes and
501 you understand the basic philosophy behind Git. You do not have to be an
502 expert in Git to be functional. A good place to look for instruction on
503 a minimal set of Git commands is
504 `here <https://git-scm.com/documentation>`__.
506 The following list of Git commands briefly describes some basic Git
509 arguments it supports. See the Git documentation for complete
512 - *git init:* Initializes an empty Git repository. You cannot use
513 Git commands unless you have a ``.git`` repository.
515 - *git clone:* Creates a local clone of a Git repository that is on
516 equal footing with a fellow developer's Git repository or an upstream
519 - *git add:* Locally stages updated file contents to the index that
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
527 pushing the change from your local Git repository into the project's
530 - *git status:* Reports any modified files that possibly need to be
534 - *git checkout branch-name:* Changes your local working branch and
538 - *git checkout -b working-branch upstream-branch:* Creates and
545 - *git branch:* Displays the existing local branches associated
549 - *git branch -D branch-name:* Deletes an existing local branch.
553 - *git pull \-\-rebase*: Retrieves information from an upstream Git
554 repository and places it in your local Git repository. You use this
560 - *git push repo-name local-branch:upstream-branch:* Sends
561 all your committed local changes to the upstream Git repository that
567 - *git merge:* Combines or adds changes from one local branch of
568 your repository with another branch. When you create a local Git
573 "main" branch, and then use the ``git merge`` command to apply the
579 - *git cherry-pick commits:* Choose and apply specific commits from
585 local Git repository. This command is a good way to graphically see
594 - *git log:* Reports a history of your commits to the repository.
598 - *git diff:* Displays line-by-line differences between a local
599 working file and the same file as understood by Git. This command is