Lines Matching refs:will
106 metadata. We'll discuss it soon, but first we will describe the ``remotes``
152 over SSH as well. Anything acceptable to Git will work.
197 Locally, this project will be cloned at path ``extra/project-1`` relative to
202 default. The current tip of this branch will be fetched and checked out as a
210 default. It will be cloned into a directory named ``proj2``. The commit
211 pointed to by the ``v1.3`` tag will be checked out when west updates the
214 - ``proj3`` has an explicit ``url``, so it will be fetched from
217 Its local path defaults to its name, ``proj3``. Commit ``abcde413a111`` will
221 Sometimes we'll refer to the ``defaults`` subsection; it will be described
243 If the project has a ``remote``, that remote's ``url-base`` will be
251 ``remote``, which will be used as the project's remote. Otherwise,
261 check out. This will be checked out as a detached HEAD by default, to
263 ``revision`` value from the ``defaults`` subsection will be used if
270 Using ``HEAD~0`` [#f1]_ as the ``revision`` will cause west to keep the current
311 HEAD, and commits not available locally, but will not fetch commits if
314 therefore west will simply checkout the locally available commit,
365 - Optional. This will be used for a project's ``remote`` if it does not
369 - Optional. This will be used for a project's ``revision`` if it does
409 repository URL will be used by default. For example, if the URL is
429 older versions of west will fail with an error message that explains the
440 # An attempt to load this manifest file with west v0.8.0 will
535 example, ``west update`` will not update inactive projects, and ``west list``
536 will not print information about them by default. As another example, any
537 :ref:`west-manifest-import` in an inactive project will be ignored by west.
1122 If ``submodules`` is ``true`` as a ``projects`` attribute, ``west update`` will
1140 Here, ``west update`` will initialize and update all submodules in ``foo``. If
1150 manually; present or not they will be completely ignored by ``west``.
1175 Here, ``west update`` will recursively initialize and update just the
1370 After ``west init``, :file:`my-downstream/my-repo` will be cloned.
1373 repository's :file:`west.yml` at revision ``v1.14.1`` will be cloned into
1409 <west-manifest-rev>` branch in the ``zephyr`` repository will be updated to
1413 The contents of :file:`zephyr/west.yml` at the new ``manifest-rev`` will then
1416 will not produce reproducible results, since the remote ``main`` branch can
1478 ``hal_nordic``, west will ignore any other definition it finds later on while
1486 When you run ``west update``, west will:
1518 This will import the following:
1679 - ``path-prefix``: Optional (new in v0.8.0). If given, this will be prepended
1689 blocked by path, then allowed by name, it will still be imported.
2043 west will not import additional manifest data from that project. If
2124 available extensions at the time the manifest is imported. They will thus take