Commit messages

Daniel van Vugt daniel.van.vugt at canonical.com
Fri Sep 27 09:41:49 UTC 2013


All,

Please put some more effort into commit messages. Recently many of them 
have become cryptic single sentences, with no bug numbers or elaboration 
in the description.

When reviewing a merge proposal this makes life hard because the 
intention of the branch is not adequately stated. When reviewing bzr 
log, this makes life hard again because there are no bug numbers 
mentioned to understand what's being fixed. So at every stage it is very 
hard to tell what's changing and why. Please use more words.

- Daniel



More information about the Mir-devel mailing list