Searched full:repositories (Results 1 – 25 of 40) sorted by relevance
12
| /Zephyr-latest/doc/develop/west/ |
| D | why.rst | 8 * The ability to work with multiple Git repositories
19 repositories is outside of the scope of this page, the fundamental requirements,
25 * **R1**: Keep externally maintained code in separately maintained repositories
27 clone each of the external repositories
31 repositories without having to make changes to the zephyr repository
56 - Does not fully support **R1**, since the externally maintained repositories
61 repositories (**R4**)
62 - Requires hardcoding of the paths/locations of the external repositories
64 Multiple Git Repositories
71 repositories in a standardized manner within the project:
[all …]
|
| D | moving-to-west.rst | 49 #. Clone the rest of the repositories used by zephyr::
54 local repositories will get out of sync. (Run ``west list`` for current
55 information on these repositories.)
|
| D | without-west.rst | 11 - cloning the additional source code repositories used by Zephyr in
13 - specifying the locations of these repositories to the Zephyr build
42 # clone additional repositories listed in zephyr/west.yml,
46 maintain those additional repositories, adding new ones as necessary
66 these repositories, the build will still work.
69 of these repositories, you must set :makevar:`ZEPHYR_MODULES`
|
| D | basics.rst | 10 (Git repositories) under a common :term:`workspace <west workspace>` directory.
84 additional Git repositories in the workspace managed by west. The manifest
92 Projects are Git repositories managed by west. Projects are defined in the
112 A workspace can contain additional Git repositories or other files and
162 This command makes sure your workspace contains Git repositories matching the
169 project repositories the new revision expects.
182 revisions should be checked out locally. Project repositories which already
|
| D | built-in.rst | 11 multiple Git repositories in the workspace.
249 - ``west diff``: run ``git diff`` in local project repositories
250 - ``west forall``: run an arbitrary command in local project repositories
251 - ``west grep``: search for patterns in local project repositories
255 - ``west status``: run ``git status`` in local project repositories
|
| D | workspaces.rst | 39 ``refs/west/foo``) for itself in local project repositories. Unlike
44 Private repositories
47 You can use west to fetch from private repositories. There is nothing
75 To use this helper for all the repositories in your workspace, run:
142 In other words, project repositories need not be located in subdirectories of
|
| D | install.rst | 24 Once west is installed, you can use it to :ref:`clone the Zephyr repositories
|
| D | manifest.rst | 21 West's view of the repositories in a :term:`west workspace`, and their
35 repositories in the workspace, with each project repository boxed in by a
42 project repositories. This relationship is shown using dotted line arrows in the
105 The ``projects`` value is a list of repositories managed by west and associated
160 repositories in the west workspace. Every project has a unique name. You can
1328 the mainline repositories.
1341 ├── [ ... other projects ...] # other mainline repositories
1563 Your Zephyr downstream has a lot of additional repositories. So many, in fact,
1633 repositories in your west workspace from a developer's forks instead of your
1899 three project repositories in an :file:`external-code` subdirectory, like this:
|
| D | release-notes.rst | 12 repositories. Currently, ``git grep``, `ripgrep`_, and standard ``grep`` are
16 active repositories, run:
558 the project and its imported repositories in a subdirectory of the workspace.
834 - Multiple repository management using Git repositories, including self-update
|
| D | extensions.rst | 240 --help`` output. If you share the updated repositories with others, they'll be
|
| D | troubleshooting.rst | 166 built-in commands for managing git repositories:
|
| /Zephyr-latest/doc/develop/ |
| D | modules.rst | 53 Modules are repositories that contain a :file:`zephyr/module.yml` file, so that
67 Module Repositories
70 * All modules included in the default manifest shall be hosted in repositories
78 new module repositories, except for repositories that are directly
79 tracking external projects (hosted in Git repositories); such modules
84 Existing module repositories that do not conform to the above convention
87 * Module repositories names should be explicitly set in the :file:`zephyr/module.yml` file.
98 It is not required in module repositories to maintain a 'master'
140 followed in all modules repositories. It is up to the module code owner
182 To facilitate management of Zephyr module repositories, the following
[all …]
|
| D | beyond-GSG.rst | 100 Cloning the Zephyr Repositories
|
| /Zephyr-latest/.github/ISSUE_TEMPLATE/ |
| D | 006_nomination.md | 42 …ocs.github.com/en/organizations/managing-access-to-your-organizations-repositories/repository-role…
|
| /Zephyr-latest/samples/net/openthread/coprocessor/ |
| D | README.rst | 68 The board support is not part of the Zephyr repositories, but the
|
| /Zephyr-latest/doc/contribute/ |
| D | bin_blobs.rst | 36 Two potential examples are Git repositories and web servers managed by
39 The Zephyr Project does not host binary blobs in its Git repositories or
49 <modules-bin-blobs>` files included in separate Zephyr :ref:`module repositories
|
| D | external.rst | 128 Such optional projects might include samples and tests in their own repositories.
|
| /Zephyr-latest/cmake/modules/ |
| D | user_cache.cmake | 81 # is good practice to have clean git repositories.
|
| /Zephyr-latest/doc/develop/application/ |
| D | index.rst | 170 ├─── <vendor/private-repositories>/
249 - add additional custom repositories of your own
250 - override repositories provided by Zephyr with your own versions
272 set of repositories in it as you wish. See :ref:`west-manifest-import` for many
273 examples of how to add or remove different repositories from your workspace as
296 the repositories you are using and updating :file:`my-manifest-repo/west.yml`
297 as needed to add and remove repositories, or change their contents.
|
| /Zephyr-latest/doc/ |
| D | glossary.rst | 167 the Git repositories which make up a :term:`west workspace`, along with
|
| /Zephyr-latest/ |
| D | west.yml | 13 # You can pass your manifest repositories to west init when creating a
|
| D | Kconfig.zephyr | 926 - dirty: one or more repositories are marked dirty
945 - dirty: one or more repositories are marked dirty
|
| /Zephyr-latest/doc/project/ |
| D | tsc.rst | 34 Gain access to relevant project repositories, documentation, and communication
|
| D | project_roles.rst | 54 <https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories/reposi…
|
| /Zephyr-latest/doc/develop/getting_started/ |
| D | index.rst | 77 repositories to meet the minimum required versions for the main
|
12
