Lines Matching refs:branch
25 As such, there are four possible ways to apply a change to the 2.7 branch:
27 … done directly to the Zephyr held code of the MCUmgr library, is backported to the ``v2.7-branch``.
28 … ported to the Zephyr held code from the upstream repository, is backported to the ``v2.7-branch``.
30 to the ``v2.7-branch``.
32 directly applied to the ``v2.7-branch``.
56 You must also apply the ``backport v2.7-branch`` label to the bug report.
84 #. Create the pull request selecting ``v2.7-branch`` as the merge target.
95 1. Create the pull request selecting ``v2.7-branch`` as the merge target.
126 Both cases are similar and differ only in the branch name.
131 1. Create a branch named as follow:
135 backport-<source>-<pr_num>-to_v2.7-branch
144 For example, a branch named ``backport-upstream-137-to-v2.7-branch`` indicates a backport of pull
147 #. Push the reviewed pull-request branch to the newly created branch and merge the backport branch
148 to ``v2.7-branch``.
154 treatment. Apply the fix directly at the top of ``v2.7-branch``.
161 applied to the ``v2.7-branch`` of the MCUmgr.