On Dec 20, 2005, at 16:45, jerry gay wrote:
... automatic generation sounds great, but it's no good
without clear commit messages. one or two word commit messages should
be shunned in favor of brief yet clear descriptions of the change,
including which parrot components are affected.
here are some guidelines for good commit messages, from my
observations:
[ ... ]
Exactly.
I've tried that mentioned svn2cl util for the 50 last revs. Due to file
moves or other global changes a lot of the created ChangeLog entries
are a meaningless mess of a list of filenames + an "oneliner". If I
need this I can still run 'svn log -v ...'
I still prefer a single line ChangeLog entry that is concise (due to
mentioned guidelines), generated automatically, and includes the
revision number for further digging.
This still will need the help of all committers to create a precise
heading line.
~jerry
