Searched refs:branches (Results 1 – 8 of 8) 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
9 function get_branch_matrix(array $branches) { argument16 }, $branches);45 function get_matrix_include(array $branches) { argument47 foreach ($branches as $branch) {68 $branches = get_branches(); variable69 $matrix_include = get_matrix_include($branches);71 echo '::set-output name=branches::' . json_encode($branches, JSON_UNESCAPED_SLASHES) . "\n";
12 branches: ${{ steps.set-matrix.outputs.branches }}18 # including all branches. This is required to find35 if: ${{ needs.GENERATE_MATRIX.outputs.branches != '[]' }}39 branch: ${{ fromJson(needs.GENERATE_MATRIX.outputs.branches) }}109 if: ${{ needs.GENERATE_MATRIX.outputs.branches != '[]' }}113 branch: ${{ fromJson(needs.GENERATE_MATRIX.outputs.branches) }}180 if: ${{ needs.GENERATE_MATRIX.outputs.branches != '[]' }}184 branch: ${{ fromJson(needs.GENERATE_MATRIX.outputs.branches) }}272 if: ${{ needs.GENERATE_MATRIX.outputs.branches != '[]' }}387 if: ${{ needs.GENERATE_MATRIX.outputs.branches != '[]' }}[all …]
12 branches:18 branches:
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 these326 Currently we have the following branches in use:343 | PHP-X.Y.Z | These branches are used for the release managers for tagging the releases, hence they…348 (i.e. 7.3) and then get merged up to all other branches. All security fixes350 needed for later branches (i.e. fixes for features which were dropped from351 later branches) an empty merge should be done.
305 In general new features should go to PECL or experimental branches until there
128 branch. Release branches for alpha/beta/.0RCx releases before the GA release216 the base branches and merged upwards as usual (e.g. commit the CVE fix to
Completed in 16 milliseconds
