- Rule 1: You do not let EMPTY commit MESSAGES.
- Rule 2: You DO NOT let EMPTY commit MESSAGES.
Each commit must have a clear, explicit and significant description.
- Rule 3: If you see unrelated, private or unfinished changes in your diff, the COMMIT is over.
Verify that the modifications are really those you want to commit. Use svn diff to double-check.
- Rule 4: Only UTILE code remains.
Remove or disable debugging code (added printf, printk ...)
- Rule 5: One MODIFICATION SUBJECT at a time.
Split your commits per subjects. Make AN UNIQUE COMMIT for a given modification.
- Rule 6: No generated files.
Unless they are mandatory for project compilation, do not add them. If you do so, commit step by step (initial version, generators, then generated files).
- Rule 7: Commit will go on as long as they have to.
This said, please be sober when commiting, and do not commit on friday after 4 pm. Really.
- Rule 8: If it is your first week in the PROJECT. You HAVE to commit.
See also Mozilla's Commiting Rules and Responsibilities...