Home
last modified time | relevance | path

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

/PHP-7.3/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.3/
H A DREADME.GIT-RULES45 Currently we have the following branches in use::
73 PHP-X.Y.Z These branches are used for the release managers for tagging
79 get merged up to all other branches. If a change is not needed for
80 later branches (i.e. fixes for features which were dropped from later
81 branches) an empty merge should be done.
H A D.appveyor.yml5 branches:
H A DCONTRIBUTING.md15 supported branch of PHP that the bug affects (only green branches on
23 Pull requests should *never* be submitted against `PHP-x.y.z` branches, as
H A DREADME.RELEASE_PROCESS42 cd pecl; mkdir foo foo/tags foo/branches; svn add foo; svn commit
166 the base branches and merged upwards as usual (f.e commit the CVE fix to 5.3,
H A DREADME.SUBMITTING_PATCH136 development branches and on "master". New PHP features only need to
H A DCODING_STANDARDS305 In general new features should go to PECL or experimental branches until

Completed in 17 milliseconds