Searched refs:submodule (Results 1 – 8 of 8) sorted by relevance
205 git submodule sync --recursive213 git submodule update --init --checkout --recursive216 git submodule update --init --rebase --recursive223 git submodule sync --recursive -- <submodule-path>225 Then it updates each submodule in the list as follows, depending on whether you231 git submodule update --init --checkout --recursive <submodule-path>234 git submodule update --init --rebase --recursive <submodule-path>236 The ``git submodule sync`` commands are skipped if the
59 delete or replace submodule definitions
1148 each desired submodule. Each submodule listed is updated recursively.1152 The ``path`` key must match exactly the path of one submodule relative1153 to its parent west project, as shown in the output of ``git submodule1155 it's not passed to ``git submodule`` commands either. The ``name`` key
161 - ``west update``: new ``--submodule-init-config`` option.406 avoids issues if the URL changes in the manifest file from when the submodule
66 git submodule update --init --recursive
354 dev$ git submodule init355 dev$ git submodule update
596 * :github:`7207` - cmake fails when zephyr is used as submodule
570 # Likely a git-submodule. Let's ask git where the real database is located.
