For writing commit messages, I think branch name may not be useful but what your commit is doing is more important maybe?
I use this syntax which is pretty much used by a lot of other open source projects like VLC or Linux: <top level artifact or commit goal>: <one line short summary of what I did> <blank line> <details, usually bullet points> <if applicable, BUG-ID, Reported-By etc.> <signature> For example in below example, I can use api (referring to the project or artifactId) or api_refactor api_refactor: moved admin level vm apis - Moved to namespace org.apache.cloudstack.api.admin - Fixed mapping in commands.properties - Fixed tabs, spaces as per coding conventions Regards. On 05-Dec-2012, at 8:09 AM, Joe Brockmeier <[email protected]> wrote: > On Tue, Dec 04, 2012 at 03:35:48PM -0500, David Nalley wrote: >> Hi folks, >> >> I'd like to propose that we change the commit message subject line from: >> >> git commit: $short_commit_msg >> >> to: >> >> git commit: $branch - $short_commit_msg >> >> Any other opinions? > > Works for me. Would be much easier to see what's going where just by > skimming the messages... > > +1 > > Best, > > jzb > -- > Joe Brockmeier > http://dissociatedpress.net/ > Twitter: @jzb
