Lines Matching refs:submodules

298    * - ``submodules``
300        submodules`_ defined by the project. See
301        :ref:`west-manifest-submodules` for details.
317 .. _Git submodules: https://git-scm.com/book/en/v2/Git-Tools-Submodules
482        - ``submodules:`` in ``projects:`` (:ref:`west-manifest-submodules`)
1097 .. _west-manifest-submodules:
1102 You can use the ``submodules`` keys briefly described :ref:`above
1104 submodules`_ configured in project's git repository. The ``submodules`` key can
1112          submodules: ...
1114 The ``submodules`` key can be a boolean or a list of mappings. We'll describe
1120 This is the easiest way to use ``submodules``.
1122 If ``submodules`` is ``true`` as a ``projects`` attribute, ``west update`` will
1123 recursively update the project's Git submodules whenever it updates the project
1127 some submodules, and you want ``west update`` to keep all of them in sync,
1137          submodules: true
1140 Here, ``west update`` will initialize and update all submodules in ``foo``. If
1141 ``bar`` has any submodules, they are ignored, because ``bar`` does not have a
1142 ``submodules`` value.
1147 The ``submodules`` key may be a list of mappings, one list element for
1149 You can still track and update unlisted submodules with ``git`` commands
1159 many submodules, and you want ``west update`` to keep some but not all of them
1169          submodules:
1176 submodules in ``foo`` with paths ``path/to/foo-first-sub`` and
1177 ``path/to/foo-second-sub``. Any submodules in ``bar`` are still ignored.