Useful things to have in a commit message: - Test plan when there's no unit test (describes how to test that the patch actually works). - Task ID (link to wha

Useful things to have in a commit message: - Test plan when there's no unit test (describes how to test that the patch actually works). - Task ID (link to whatever is used to track tasks/bugs, as there's usually more context there). - Blame rev when a patch fixes a bug, it's useful to know which commit introduced the bug.