On 06-Dec-2012, at 9:17 AM, Joe Brockmeier <[email protected]> wrote: > On Thu, Dec 6, 2012, at 11:14 AM, Rohit Yadav wrote: >> For writing commit messages, I think branch name may not be useful but >> what your commit is doing is more important maybe? > > As I understand it, this is a proposal for the subject line of the > emails - not how the commit messages are written.
Okay, is it for the git hook to send emails with branch names in the message lines? Yes, that would be great! Oops, got confused. Regards. > >> 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 >> > > > -- > Joe Brockmeier > [email protected] > Twitter: @jzb > http://www.dissociatedpress.net/
