Lines Matching refs:patch
4 This document describes how to submit an enhancement or patch for PHP.
27 bug can be used to track the patch progress and prevent your changes
44 Attach the patch to the PHP bug and consider sending a notification
46 extension maintainer. Explain what has been changed by your patch.
49 Please make the mail subject prefix "[PATCH]". If attaching a patch,
53 The preferred way to propose PHP patch is sending pull request from
69 to track the patch progress and prevent your changes getting lost in
79 Attach the patch to the PHP bug and consider sending a notification
81 fixed/added/changed by your patch.
84 which can be closed by your patch. If attaching a patch, ensure it
93 can be used to track the patch progress and prevent your changes
109 Update any open bugs and add a link to the source of your patch. Send
110 the patch or pointer to the bug to pecl-dev@lists.php.net. Also CC
112 patch. Test scripts should be included.
114 Please make the mail subject prefix "[PATCH] ...". Include the patch
126 How to create your PHP, PHP Documentation or PECL patch
146 After testing is finished, create a patch file using the command:
154 Checklist for submitting your PHP or PECL code patch
161 - Run "make test" to check your patch doesn't break other features.
165 - Rebuild PHP with --enable-maintainer-zts to check your patch
167 - Review the patch once more just before submitting it.
170 What happens after submitting your PHP, PHP Documentation or PECL patch
172 If your patch is easy to review and obviously has no side-effects,
177 few days, consider resubmitting the patch. Before doing this think
180 - Did I send the patch to the right mail list?
183 - Did I explain my patch clearly?
184 - Is my patch too hard to review? Because of what factors?
187 What happens when your PHP or PECL patch is applied
190 patch affects end users, a brief description and your name might be
