There appears to be a general trend towards short commit messages. I don't impose a "must have a long log and short log" policy but I'll have to if things don't improve.
To be clear, the commit message needs to say not just what changed but *why* the change is necessary, e.g. what error it causes without it. Commit messages need to stand alone without reference to any linked bugzilla entry either, that is just there as a way to further look at the issue. I'm going to be getting stricter about this. Cheers, Richard _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
