Searched full:branches (Results 1 – 25 of 49) sorted by relevance
12
1 .. _code-flow-and-branches:3 Code Flow and Branches9 The zephyr Git repository has three types of branches:15 Collaboration branches that are used for shared development17 collaboration branch requires a justification and TSC approval. Collaboration branches24 Branches which track maintenance releases based on a major27 Development in collaboration branches before features go to mainline allows teams to40 Collaboration branches are ephemeral and shall be removed once the collaboration work55 - All changes to collaboration branches shall come in form of github pull requests.
49 we will use the term branch also when referencing branches not in the same
31 In order to get a true benchmark, there should be as few branches38 In order to get a true benchmark, there should be as few branches
8 branches:15 branches:
8 branches:19 branches:
9 branches:16 branches:
5 branches:10 branches:
5 branches: [main]
8 branches:17 branches:
7 branches:
5 branches:
10 branches:
6 branches:
11 branches: [main]
15 branches:
8 branches:
138 leaving behind any branches which were already checked out. This is139 typically a safe operation that will not modify any of your local branches.148 If you would rather rebase any locally checked out branches instead, use151 If you would like ``west update`` to keep local branches checked out as171 does not even try to rebase and leaves your branches behind just like a174 your branches in place.
11 * DT macros for clock branches.
43 * - Structural test coverage(entry points,statements,branches)155 * - Structural test coverage(entry points,statements,branches)
69 without tests or branches, for all list modification primitives.
