Home
last modified time | relevance | path

Searched refs:branches (Results 1 – 7 of 7) sorted by relevance

/PHP-7.4/sapi/phpdbg/
H A Dphpdbg_btree.c25 branch = branch->branches[!!(n)];
52 if (branch->branches[1]) { in phpdbg_btree_find()
58 if (branch->branches[0]) { in phpdbg_btree_find()
80 if (branch->branches[0]) { in phpdbg_btree_find_closest()
100 CHOOSE_BRANCH(branch->branches[1]); in phpdbg_btree_find_closest()
106 if (branch->branches[1]) { in phpdbg_btree_find_closest()
107 if (branch->branches[0]) { in phpdbg_btree_find_closest()
114 CHOOSE_BRANCH(branch->branches[1]); in phpdbg_btree_find_closest()
189 if (branch->branches[0] && branch->branches[1]) { in phpdbg_btree_delete()
194 branch = branch->branches[(idx >> i) % 2]; in phpdbg_btree_delete()
[all …]
H A Dphpdbg_btree.h33 phpdbg_btree_branch *branches[2]; member
/PHP-7.4/
H A Dazure-pipelines.yml3 branches:
17 branches:
H A D.appveyor.yml5 branches:
H A DCONTRIBUTING.md35 supported branch of PHP that the bug affects (only green branches on
43 Pull requests should *never* be submitted against `PHP-x.y.z` branches, as these
329 Currently we have the following branches in use:
346 | PHP-X.Y.Z | These branches are used for the release managers for tagging the releases, hence they…
351 (i.e. 7.3) and then get merged up to all other branches. All security fixes
353 needed for later branches (i.e. fixes for features which were dropped from
354 later branches) an empty merge should be done.
H A DCODING_STANDARDS.md326 In general new features should go to PECL or experimental branches until there
/PHP-7.4/docs/
H A Drelease-process.md127 branch. Release branches for alpha/beta/.0RCx releases before the GA release
213 the base branches and merged upwards as usual (e.g. commit the CVE fix to

Completed in 26 milliseconds