Searched refs:branches (Results 1 – 8 of 8) sorted by relevance
25 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 …]
33 phpdbg_btree_branch *branches[2]; member
45 Currently we have the following branches in use::73 PHP-X.Y.Z These branches are used for the release managers for tagging79 get merged up to all other branches. If a change is not needed for80 later branches (i.e. fixes for features which were dropped from later81 branches) an empty merge should be done.
5 branches:
15 supported branch of PHP that the bug affects (only green branches on23 Pull requests should *never* be submitted against `PHP-x.y.z` branches, as
42 cd pecl; mkdir foo foo/tags foo/branches; svn add foo; svn commit166 the base branches and merged upwards as usual (f.e commit the CVE fix to 5.3,
136 development branches and on "master". New PHP features only need to
305 In general new features should go to PECL or experimental branches until
Completed in 17 milliseconds