Confirmed users, Bureaucrats and Sysops emeriti
674
edits
(→Ideas For How To Split Your Patch: "and then") |
No edit summary |
||
| Line 1: | Line 1: | ||
== The Short Version == | |||
Basically, the bottom line is that small, simple patches will get through the review process much faster. | Basically, the bottom line is that small, simple patches will get through the review process much faster. | ||
| Line 5: | Line 7: | ||
All patches should address ''only one thing''. If you are implementing a huge feature, try to figure out how to split it up into many small patches that build on each other, and file separate bugs for each one of your small patches. | All patches should address ''only one thing''. If you are implementing a huge feature, try to figure out how to split it up into many small patches that build on each other, and file separate bugs for each one of your small patches. | ||
== Longer Explanation == | == A Longer Explanation == | ||
It is a good idea to split your changes up into multiple simple patches. Simple patches are easier to review, because: | It is a good idea to split your changes up into multiple simple patches. Simple patches are easier to review, because: | ||