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
45 The preferred way to propose PHP patch is sending pull request from
54 If you are not using GitHub, attach your patch to a PHP bug and
57 extension maintainer. Explain what has been changed by your patch.
60 Please make the mail subject prefix "[PATCH]". If attaching a patch,
70 to track the patch progress and prevent your changes getting lost in
80 Attach the patch to the PHP bug and consider sending a notification
82 fixed/added/changed by your patch.
85 which can be closed by your patch. If attaching a patch, ensure it
94 can be used to track the patch progress and prevent your changes
110 Update any open bugs and add a link to the source of your patch. Send
111 the patch or pointer to the bug to pecl-dev@lists.php.net. Also CC
113 patch. Test scripts should be included.
115 Please make the mail subject prefix "[PATCH] ...". Include the patch
127 How to create your PHP, PHP Documentation or PECL patch
147 After testing is finished, create a patch file using the command:
155 Checklist for submitting your PHP or PECL code patch
162 - Run "make test" to check your patch doesn't break other features.
166 - Rebuild PHP with --enable-maintainer-zts to check your patch
168 - Review the patch once more just before submitting it.
171 What happens after submitting your PHP, PHP Documentation or PECL patch
173 If your patch is easy to review and obviously has no side-effects,
178 few days, consider resubmitting the patch. Before doing this think
181 - Did I send the patch to the right mail list?
184 - Did I explain my patch clearly?
185 - Is my patch too hard to review? Because of what factors?
188 What happens when your PHP or PECL patch is applied
191 patch affects end users, a brief description and your name might be
