Lines Matching full:git
32 The history of the manifest repository is the line of Git commits which is
34 using solid arrows. The plane below contains the Git commit history of the
116 the complete Git fetch URL for each project. A project's fetch URL can be set
128 url-base: https://git.example.com/base1
130 url-base: https://git.example.com/base2
149 bases are respectively ``https://git.example.com/base1`` and
150 ``https://git.example.com/base2``. You can use SSH URL bases as well; for
151 example, you might use ``git@example.com:base1`` if ``remote1`` supported Git
152 over SSH as well. Anything acceptable to Git will work.
161 specify what Git remote URLs to use when cloning and fetching the projects,
193 - ``proj1`` has remote ``remote1``, so its Git fetch URL is
194 ``https://git.example.com/base1/proj1``. The remote ``url-base`` is appended
206 ``https://git.example.com/base2/my-path``. The ``repo-path`` attribute, if
248 remote Git repository.
260 - Optional. The Git revision that ``west update`` should
299 - Optional. You can use this to make ``west update`` also update `Git
309 .. [#f1] In git, HEAD is a reference, whereas HEAD~<n> is a valid revision but
317 .. _Git submodules: https://git-scm.com/book/en/v2/Git-Tools-Submodules
336 url-base: https://git.example.com/base1
338 url-base: https://git.example.com/base2
410 ``https://git.example.com/project-repo``, the manifest repository would
723 url-base: https://git.example.com
755 url-base: https://git.example.com
786 url-base: https://git.example.com
815 url-base: https://git.example.com
850 url-base: https://git.example.com
885 url-base: https://git.example.com
918 url-base: https://git.example.com
964 url: https://git.example.com/child
967 url: https://git.example.com/project-1
980 url: https://git.example.com/project-2
982 url: https://git.example.com/project-3
1007 url: https://git.example.com/child
1010 url: https://git.example.com/project-1
1023 url: https://git.example.com/project-2
1027 url: https://git.example.com/project-3
1054 url: https://git.example.com/child
1057 url: https://git.example.com/project-1
1070 url: https://git.example.com/project-2
1074 url: https://git.example.com/project-3
1099 Git Submodules in Projects
1103 <west-manifest-files>` to force ``west update`` to also handle any `Git
1104 submodules`_ configured in project's git repository. The ``submodules`` key can
1123 recursively update the project's Git submodules whenever it updates the project
1149 You can still track and update unlisted submodules with ``git`` commands
1153 to its parent west project, as shown in the output of ``git submodule
1155 it's not passed to ``git submodule`` commands either. The ``name`` key
1244 additional files defined in that project's Git history.
1297 :file:`west.yml` from the ``p1`` git repository at revision ``v1.0``:
1306 import: true # Import west.yml from p1's v1.0 git tag
1362 ``my-repo`` is hosted at ``https://git.example.com/my-repo``:
1366 west init -m https://git.example.com/my-repo my-downstream
1404 west init -m https://git.example.com/my-repo my-downstream
1446 url-base: https://git.example.com
1472 - is cloned from ``https://git.example.com/hal_nordic`` instead of
1528 Notice how ``projects`` imports get data from Git using ``manifest-rev``, while
1699 hosted at ``https://git.example.com/mainline/manifest``.
1708 url: https://git.example.com/mainline/app
1711 url: https://git.example.com/mainline/lib
1714 url: https://git.example.com/mainline/lib2
1720 url: https://git.example.com/mainline/manifest
1726 url: https://git.example.com/downstream/app
1729 url: https://git.example.com/downstream/lib3
1738 url: https://git.example.com/mainline/manifest
1740 url: https://git.example.com/downstream/app
1743 url: https://git.example.com/downstream/lib3
1746 url: https://git.example.com/mainline/app
1749 url: https://git.example.com/mainline/lib2
1769 url: https://git.example.com/mainline/app
1772 url: https://git.example.com/mainline/lib
1775 url: https://git.example.com/mainline/lib2
1781 url: https://git.example.com/mainline/manifest
1785 url: https://git.example.com/downstream/app
1788 url: https://git.example.com/downstream/lib3
1798 url: https://git.example.com/mainline/lib
1801 url: https://git.example.com/mainline/lib2
1803 url: https://git.example.com/mainline/manifest
1805 url: https://git.example.com/downstream/app
1808 url: https://git.example.com/downstream/lib3
1827 url-base: https://git.example.com/mainline
1845 url: https://git.example.com/mainline/manifest
1850 url: https://git.example.com/downstream/hal_foo
1861 url-base: https://git.example.com/mainline
1869 repo-path: https://git.example.com/mainline/manifest
1872 url: https://git.example.com/downstream/hal_foo
1893 url-base: https://git.example.com
1916 url: https://git.example.com/foo
1930 url-base: https://git.example.com
2091 from Git at the latest ``manifest-rev`` revisions in their projects. These
2101 as well as updating the ``manifest-rev`` branch in the local git clone of