Lines Matching refs:a
26 create a bug or identify an existing bug at http://bugs.php.net/. A
30 If your change is large then create a Request For Comment (RFC) page
48 Fork the official PHP repository and send a pull request. A
49 notification will be sent to the pull request mailing list. Sending a
54 If you are not using GitHub, attach your patch to a PHP bug and
55 consider sending a notification email about the change to
60 Please make the mail subject prefix "[PATCH]". If attaching a patch,
61 ensure it has a file extension of ".txt". This is because only MIME
68 If you are fixing incorrect PHP documentation first create a bug or
80 Attach the patch to the PHP bug and consider sending a notification
85 which can be closed by your patch. If attaching a patch, ensure it
86 has a file extension of ".txt". This is because only MIME attachments
92 If you are fixing broken functionality in a PECL extension then create
93 a bug or identify an existing bug at http://bugs.php.net/. A bug
97 If your change is large then create a Request For Comment (RFC) page
110 Update any open bugs and add a link to the source of your patch. Send
116 as an attachment with a file extension of ".txt". This is because
147 After testing is finished, create a patch file using the command:
176 Because PHP is a volunteer-driven effort more complex patches will
177 require patience on your side. If you do not receive feedback in a
191 patch affects end users, a brief description and your name might be