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,
58 to track the patch progress and prevent your changes getting lost in
68 Attach the patch to the PHP bug and consider sending a notification
70 fixed/added/changed by your patch.
73 which can be closed by your patch. If attaching a patch, ensure it
82 can be used to track the patch progress and prevent your changes
98 Update any open bugs and add a link to the source of your patch. Send
99 the patch or pointer to the bug to pecl-dev@lists.php.net. Also CC
101 patch. Test scripts should be included.
103 Please make the mail subject prefix "[PATCH] ...". Include the patch
115 How to create your PHP, PHP Documentation or PECL patch
135 After testing is finished, create a patch file using the command:
143 Checklist for submitting your PHP or PECL code patch
150 - Run "make test" to check your patch doesn't break other features.
154 - Rebuild PHP with --enable-maintainer-zts to check your patch
156 - Review the patch once more just before submitting it.
159 What happens after submitting your PHP, PHP Documentation or PECL patch
161 If your patch is easy to review and obviously has no side-effects,
166 few days, consider resubmitting the patch. Before doing this think
169 - Did I send the patch to the right mail list?
172 - Did I explain my patch clearly?
173 - Is my patch too hard to review? Because of what factors?
176 What happens when your PHP or PECL patch is applied
179 patch affects end users, a brief description and your name might be
