Searched refs:branch (Results 1 – 14 of 14) sorted by relevance
/PHP-5.4/tests/lang/ |
H A D | 020.phpt | 11 echo "In branch 1\n"; 47 In branch 1 50 In branch 1 53 In branch 1 56 In branch 1 59 In branch 1 62 In branch 1 65 In branch 1 68 In branch 1 71 In branch 1 [all …]
|
H A D | 021.phpt | 12 echo "In branch 0\n"; 15 echo "In branch 1\n"; 18 echo "In branch 2\n"; 21 echo "In branch 3\n"; 24 echo "In branch 4\n"; 35 In branch 0 37 In branch 1 39 In branch 2 41 In branch 3
|
/PHP-5.4/ |
H A D | README.GIT-RULES | 28 confirmation from the release manager for the given branch. 46 master The active development branch. 57 PHP-5.3 This branch is closed. 59 PHP-5.2 This branch is closed. 61 PHP-5.1 This branch is closed. 63 PHP-4.4 This branch is closed. 70 1. All changes should first go to the lowest branch (i.e. 5.6) and then
|
H A D | README.RELEASE_PROCESS | 30 - Create an directory for the extension incl. branch and tag structure, 54 3. Checkout the release branch for this release (e.g., PHP-5.4.2) from the main branch. 65 7. If all is right, commit the changes to the release branch with ``git commit -a``. 67 8. Tag the repository release branch with the version, e.g.: 71 in the *main* branch (PHP-5.4 for example) to prepare for the **next** version. 74 Commit the changes to the main branch. 76 10. Push the changes to the main repo, the tag, the main branch and the release branch : 78 ``git push origin {main branch}`` 79 ``git push origin {release branch}`` 144 merge to 5.4, 5.5 etc...). Then you can cherry-pick it in your release branch. [all …]
|
H A D | NEWS | 822 bug #62691, and bug #63706) from PHP 5.5 branch
|
/PHP-5.4/Zend/tests/traits/bugs/ |
H A D | abstract-methods06.phpt | 2 …re of abstract methods should be checked. (also checking the second possible implementation branch)
|
/PHP-5.4/win32/build/ |
H A D | mkdist.php | 260 $branch = "HEAD"; // TODO - determine this from SVN branche name variable 269 Branch: $branch
|
/PHP-5.4/ext/pcre/pcrelib/ |
H A D | ChangeLog | 645 case when an overflowing capture is in a branch that is subsequently 1210 /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never 1487 successfully matched, but the branch in which it appeared failed, the 1659 to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it 1932 item in branch that calls a recursion is a subroutine call - as in the 1933 second branch in the above example - was incorrectly given the compile- 1954 the pattern is reset in the first branch, pcre_compile() failed with 2307 19. A conditional group that had only one branch was not being correctly 3318 20. Extended pcre_study() to be more clever in cases where a branch of a 4679 subpattern starts with (?(R) the "true" branch is used if recursion has [all …]
|
H A D | HACKING | 423 subpattern entirely is a valid branch. In the case of the first two, not
|
/PHP-5.4/ext/pcre/pcrelib/doc/ |
H A D | pcre.txt | 1408 previous branch point in the tree, and tries the next alternative 1409 branch at that level. This often involves backing up (moving to the 2460 54 DEFINE group contains more than one branch 2755 branch starts with "^", or 2757 (b) every branch of the pattern starts with ".*" and PCRE_DOTALL is not 2788 branch starts with "^", or 2790 (b) every branch of the pattern starts with ".*" and PCRE_DOTALL is not 4664 strings, each alternative branch of a lookbehind assertion can match a 4917 | start of alternative branch 6092 # before ---------------branch-reset----------- after [all …]
|
/PHP-5.4/ext/imap/ |
H A D | php_imap.c | 4681 if(cur->branch) { in build_thread_tree_helper() 4684 build_thread_tree_helper(cur->branch, tree, numNodes, buf); in build_thread_tree_helper()
|
/PHP-5.4/ext/mbstring/oniguruma/ |
H A D | HISTORY | 901 2004/03/16: [memo] 2.X branch for 8-bit encodings only.
|
/PHP-5.4/win32/ |
H A D | install.txt | 558 Option Pack branch or the Control Panel=>Administrative Tools under
|
/PHP-5.4/ext/pcre/pcrelib/testdata/ |
H A D | testoutput2 | 7877 Failed: DEFINE group contains more than one branch at offset 22
|
Completed in 151 milliseconds