Searched refs:branches (Results 1 – 9 of 9) sorted by relevance
23 branch = branch->branches[!!(n)];50 if (branch->branches[1]) { in phpdbg_btree_find()56 if (branch->branches[0]) { in phpdbg_btree_find()78 if (branch->branches[0]) { in phpdbg_btree_find_closest()98 CHOOSE_BRANCH(branch->branches[1]); in phpdbg_btree_find_closest()104 if (branch->branches[1]) { in phpdbg_btree_find_closest()105 if (branch->branches[0]) { in phpdbg_btree_find_closest()112 CHOOSE_BRANCH(branch->branches[1]); in phpdbg_btree_find_closest()187 if (branch->branches[0] && branch->branches[1]) { in phpdbg_btree_delete()192 branch = branch->branches[(idx >> i) % 2]; in phpdbg_btree_delete()[all …]
31 phpdbg_btree_branch *branches[2]; member
14 branches: ${{ steps.set-matrix.outputs.branches }}19 # including all branches. This is required to find42 if: ${{ needs.GENERATE_MATRIX.outputs.branches != '[]' }}47 branch: ${{ fromJson(needs.GENERATE_MATRIX.outputs.branches) }}
16 branches:34 branches:
59 $branches = $branch === 'master' variable64 fwrite($f, 'branches=' . json_encode($branches, JSON_UNESCAPED_SLASHES) . "\n");
35 supported branch of PHP that the bug affects (only green branches on43 Pull requests should *never* be submitted against `PHP-x.y.z` branches, as these327 Currently we have the following branches in use:345 | PHP-X.Y.Z | These branches are used for the release managers for tagging the releases, hence they…350 (i.e. 7.3) and then get merged up to all other branches. All security fixes352 needed for later branches (i.e. fixes for features which were dropped from353 later branches) an empty merge should be done.
286 In general, new features should go to PECL or experimental branches until there
109 Non stable release branches don't need to be pushed 197 the base branches and merged upwards as usual (e.g. commit the CVE fix to
1216 || // Combine the following two branches.
Completed in 35 milliseconds
