@@ -5,7 +5,7 @@ This document describes how to submit an enhancement or patch for PHP.
5
5
It's easy!
6
6
7
7
You don't need any login accounts or special access to download,
8
- build, debug and begin submitting PHP, PECL or PEAR code, tests or
8
+ build, debug and begin submitting PHP or PECL code, tests or
9
9
documentation. Once you've followed this README and had several
10
10
patches accepted, commit privileges are often quickly granted.
11
11
@@ -16,8 +16,8 @@ http://phpadvent.org/2008/less-whining-more-coding-by-elizabeth-smith
16
16
Online Forums
17
17
-------------
18
18
There are several IRC channels where PHP developers are often
19
- available to discuss questions. They include #php.pecl, #php.doc and
20
- #pear on the EFNet network and #php-dev-win on FreeNode.
19
+ available to discuss questions. They include #php.pecl and #php.doc
20
+ on the EFNet network and #php-dev-win on FreeNode.
21
21
22
22
23
23
PHP Patches
@@ -78,7 +78,7 @@ of type 'text/*' are accepted.
78
78
PECL Extension Patches: http://pecl.php.net/
79
79
--------------------------------------------
80
80
If you are fixing broken functionality in a PECL extension then create
81
- a bug or identify an existing bug at http://pecl .php.net/bugs /. A bug
81
+ a bug or identify an existing bug at http://bugs .php.net/. A bug
82
82
can be used to track the patch progress and prevent your changes
83
83
getting lost in the PHP mail archives.
84
84
@@ -114,15 +114,15 @@ http://pear.php.net/manual/en/guide-developers.php
114
114
115
115
How to create your PHP, PHP Documentation or PECL patch
116
116
-------------------------------------------------------
117
- PHP and PECL use Subversion (SVN) for revision control. Read
118
- http://www.php.net/svn .php for help on using SVN to get and build PHP
119
- source code. We recommend using a Sparse Directory checkout described
120
- in http ://wiki.php.net/vcs/svnfaq. If you are new to SVN, read
121
- http ://svnbook.red-bean.com .
117
+ PHP and most PECL packages use Git for revision control. Some PECL
118
+ packages use Subversion (SVN) Read http://www.php.net/git .php for help
119
+ on using Git to get and build PHP source code. We recommend to look
120
+ at our workflow on https ://wiki.php.net/vcs/gitworkflow and our FAQ
121
+ https ://wiki.php.net/vcs/gitfaq .
122
122
123
123
Generally we ask that bug fix patches work on the current stable PHP
124
- development branches and on "trunk ". New PHP features only need to
125
- work on "trunk ".
124
+ development branches and on "master ". New PHP features only need to
125
+ work on "master ".
126
126
127
127
Read CODING_STANDARDS before you start working.
128
128
@@ -134,15 +134,15 @@ comprehensive.
134
134
135
135
After testing is finished, create a patch file using the command:
136
136
137
- svn diff > your_patch.txt
137
+ git diff > your_patch.txt
138
138
139
139
For ease of review and later troubleshooting, submit individual
140
140
patches for each bug or feature.
141
141
142
142
143
143
Checklist for submitting your PHP or PECL code patch
144
144
----------------------------------------------------
145
- - Update SVN source just before running your final 'diff' and
145
+ - Update git source just before running your final 'diff' and
146
146
before testing.
147
147
- Add in-line comments and/or have external documentation ready.
148
148
Use only "/* */" style comments, not "//".
@@ -175,7 +175,7 @@ about these questions:
175
175
176
176
What happens when your PHP or PECL patch is applied
177
177
---------------------------------------------------
178
- Your name will likely be included in the SVN commit log. If your
178
+ Your name will likely be included in the Git commit log. If your
179
179
patch affects end users, a brief description and your name might be
180
180
added to the NEWS file.
181
181
0 commit comments