| | 4 | |
| | 5 | == General Guidelines == |
| | 6 | |
| | 7 | * Try to make small patches (i.e. work in consistent increments). |
| | 8 | |
| | 9 | * Separate changes that affect functionality from those that just affect |
| | 10 | code layout, indendation, whitespace, filenames etc. This means that |
| | 11 | when looking at patches later, we don't have to wade through loads of |
| | 12 | non-functional changes to get to the important parts of the patch. |
| | 13 | |
| | 14 | * If possible, record often. This helps to avoid conflicts. |
| | 15 | |
| | 16 | * Do not push conflicts (see [wiki:WorkingConventions/Darcs#Conflicts]). |
| | 17 | |
| | 18 | * Every patch must pass at least minimal validation: see TestingPatches. |
| | 19 | |
| | 20 | * Discuss anything you think might be controversial before pushing it. |
