Home
last modified time | relevance | path

Searched refs:repo (Results 1 – 25 of 49) sorted by relevance

12

/Zephyr-Core-3.7.0/scripts/release/
Dlist_backports.py121 def __init__(self, repo, base, pulls): argument
123 self._repo = repo
131 def by_date_range(repo, base, start_date, end_date, excludes): argument
138 unfiltered_pulls = repo.get_pulls(
158 return Backport(repo, base, pulls)
161 def by_included_prs(repo, base, includes): argument
169 p = repo.get_pull(i)
187 return Backport(repo, base, pulls)
299 repo = gh.get_repo(args.org + '/' + args.repo)
306 bp = Backport.by_included_prs(repo, args.base, set(args.includes))
[all …]
/Zephyr-Core-3.7.0/scripts/footprint/
Dupload_data.py99 repo = Repo(zephyr_base)
124 gitcommit = repo.commit(f'{commit}')
128 gitcommit = repo.commit(f'{commit[cidx:]}')
/Zephyr-Core-3.7.0/
DCONTRIBUTING.rst27 * Source code for the project is maintained in the GitHub repo:
30 * Issue and feature tracking is done using GitHub issues in this repo.
/Zephyr-Core-3.7.0/boards/quicklogic/qomu/doc/
Dindex.rst58 Refer to `TinyFPGA Programmer Application repo`_ for detailed information on installation
76 .. _TinyFPGA Programmer Application repo:
/Zephyr-Core-3.7.0/doc/develop/west/
Dmanifest.rst27 :alt: West multi-repo history
30 West multi-repo history
184 repo-path: my-path
205 - ``proj2`` has a ``remote`` and a ``repo-path``, so its fetch URL is
206 ``https://git.example.com/base2/my-path``. The ``repo-path`` attribute, if
244 combined with the project's ``name`` (or ``repo-path``, if it has one)
254 * - ``repo-path``
257 Projects may not have both ``url`` and ``repo-path`` attributes.
349 repo-path: my-path
410 ``https://git.example.com/project-repo``, the manifest repository would
[all …]
Dwhy.rst41 Google's `repo <https://gerrit.googlesource.com/git-repo/>`_.
47 * Google repo
Dworkspaces.rst268 - Analogy with existing mechanisms: Google repo-based source distribution
285 ├── manifest-repo/ # .git/ never modified by west
296 Here is an example T3 :file:`manifest-repo/west.yml` which uses
320 path: manifest-repo
Dbasics.rst13 :term:`west workspace`, and clones the :term:`manifest repo <west manifest
31 ├── zephyr/ # .git/ repo
/Zephyr-Core-3.7.0/scripts/west_commands/
DREADME.txt7 on the multi-repo need to be in upstream west, not here. Try to limit
/Zephyr-Core-3.7.0/doc/develop/toolchains/
Dcrosstool_ng.rst22 You will need to clone the ``sdk-ng`` repo and run the following command:
/Zephyr-Core-3.7.0/subsys/
DCMakeLists.txt5 # is pulled in as though the source files are in main repo. This results in
/Zephyr-Core-3.7.0/samples/tfm_integration/tfm_regression_test/
DREADME.rst14 The TF-M regression tests are implemented in the tf-m-tests repo: https://git.trustedfirmware.org/T…
16 This sample is available for platforms that are supported in the trusted-firmware-m repo: https://g…
/Zephyr-Core-3.7.0/doc/
Dindex.rst28 the LICENSE file in the project's `GitHub repo`_). The Zephyr OS also
128 .. _GitHub repo: https://github.com/zephyrproject-rtos/zephyr
/Zephyr-Core-3.7.0/scripts/ci/stats/
Dmerged_prs.py142 gh_repo = gh.get_repo(args.repo)
/Zephyr-Core-3.7.0/boards/adafruit/itsybitsy/doc/
Dindex.rst144 ItsyBitsy bootloader can be found in the `Adafruit nRF52 Bootloader repo`_.
191 .. _Adafruit nRF52 Bootloader repo:
/Zephyr-Core-3.7.0/doc/connectivity/bluetooth/autopts/
Dautopts-win10.rst140 In Git Bash, clone project repo:
230 This command will force the irreversible removal of all uncommitted files in the repo.
/Zephyr-Core-3.7.0/doc/hardware/porting/
Dsoc_porting.rst47 to Zephyr, but if your SoC is placed in a local repo, then any folder
48 structure under ``<your-repo>/soc`` is permitted.
147 SoC devicetree include files are located in the :file:`<zephyr-repo>/dts` folder
/Zephyr-Core-3.7.0/samples/tfm_integration/psa_protected_storage/
DREADME.rst27 This sample is available for platforms that are supported in the trusted-firmware-m repo:
/Zephyr-Core-3.7.0/samples/tfm_integration/tfm_psa_test/
DREADME.rst11 The PSA tests are implemented in the psa-arch-tests repo: https://github.com/ARM-software/psa-arch-…
/Zephyr-Core-3.7.0/doc/introduction/
Dindex.rst39 project's `GitHub repo`_). There are some
46 .. _GitHub repo: https://github.com/zephyrproject-rtos/zephyr
/Zephyr-Core-3.7.0/doc/develop/application/
Dindex.rst115 | <zephyr-repo-app>` | |
127 .. _zephyr-repo-app:
262 git clone https://github.com/zephyrproject-rtos/example-application my-manifest-repo
263 west init -l my-manifest-repo
266 :file:`my-manifest-repo` as the manifest repository. The :file:`my-workspace`
267 and :file:`my-manifest-repo` names are arbitrary: change them as needed.
271 can then edit :file:`my-manifest-repo/west.yml` to your liking, changing the
284 If you push the resulting :file:`my-manifest-repo` repository somewhere else,
286 repository to ``https://git.example.com/my-manifest-repo``. Other people can
291 west init -m https://git.example.com/my-manifest-repo my-workspace
[all …]
/Zephyr-Core-3.7.0/doc/develop/
Dbeyond-GSG.rst103 The Zephyr project source is maintained in the `GitHub zephyr repo
124 repo.
251 file by downloading it from their sourceforge repo, or if you've
/Zephyr-Core-3.7.0/doc/contribute/
Dguidelines.rst26 .. _GitHub repo: https://github.com/zephyrproject-rtos/zephyr
29 the project's `GitHub repo`_) to strike a balance between open
569 before pushing on zephyr repo. To do this, make the file
764 right corner of the Zephyr project repo page in GitHub.)
819 #. Commit your changes to your local repo::
833 #. In your web browser, go to your forked repo and click on the
842 MAINTAINERS file in the repo). If you are a project member, you can
866 commit(s) to fix review issues. In your development repo::
/Zephyr-Core-3.7.0/scripts/
Dset_assignees.py315 for repo in repos:
/Zephyr-Core-3.7.0/samples/subsys/usb/dfu/
DREADME.rst156 .. _MCUboot GitHub repo: https://github.com/zephyrproject-rtos/mcuboot

12