Lines Matching full:downstream

1323 Example 1.1: Downstream of a Zephyr release
1334    my-downstream/
1342    └── my-repo/                   # your downstream repository
1366    west init -m https://git.example.com/my-repo my-downstream
1367    cd my-downstream
1370 After ``west init``, :file:`my-downstream/my-repo` will be cloned.
1374 :file:`my-downstream` as well.
1381 Example 1.2: "Rolling release" Zephyr downstream
1404    west init -m https://git.example.com/my-repo my-downstream
1405    cd my-downstream
1429 Example 1.3: Downstream of a Zephyr release, with module fork
1434 - is a downstream of Zephyr 2.0
1435 - includes a downstream fork of the :file:`modules/hal/nordic`
1534 Example 2.1: Downstream of a Zephyr release with explicit path
1560 Example 2.2: Downstream with directory of manifest files
1563 Your Zephyr downstream has a lot of additional repositories. So many, in fact,
1693 Example 3.1: Downstream with name allowlist
1697 downstream. The downstream doesn't want to use all the mainline
1716    # downstream west.yml:
1725        - name: downstream-app
1726          url: https://git.example.com/downstream/app
1729          url: https://git.example.com/downstream/lib3
1739        - name: downstream-app
1740          url: https://git.example.com/downstream/app
1743          url: https://git.example.com/downstream/lib3
1756 Example 3.2: Downstream with path allowlist
1777    # downstream west.yml:
1785          url: https://git.example.com/downstream/app
1788          url: https://git.example.com/downstream/lib3
1805          url: https://git.example.com/downstream/app
1808          url: https://git.example.com/downstream/lib3
1812 Example 3.3: Downstream with path blocklist
1841    # downstream west.yml:
1850          url: https://git.example.com/downstream/hal_foo
1872          url: https://git.example.com/downstream/hal_foo
1949 Example 4.1: Downstream with sequence of manifest files