On Sat, Jan 2, 2010 at 12:12 AM, Trans <transf...@gmail.com> wrote:
>
>
> On Jan 1, 7:43 pm, Jeffrey <jefr...@gmail.com> wrote:
>> This sounds like precisely the purpose of standard formats for log
>> messages.  The simplest thing would be to prefix the subject with
>> "[type]:" like this:
>>
>> major: add big feature
>>
>> ....
>>
>> or put it on the first line of the body, if you have something else
>> you like to do with the subject, whatever.  As long as your format is
>> standard, you can easily search for that particular key.
>>
>> Jeffrey
>
> Yes. That is what I currently do. It works okay, but I would prefer
> something more formal/strict if possible. It's very easy to fail to
> conform to a log message convention.

Well if you HAVE to be formal/strict you might want to look at the
prepare-commit-msg and/or commit-msg hooks

http://book.git-scm.com/5_git_hooks.html

-- 
Rick DeNatale

Blog: http://talklikeaduck.denhaven2.com/
Twitter: http://twitter.com/RickDeNatale
WWR: http://www.workingwithrails.com/person/9021-rick-denatale
LinkedIn: http://www.linkedin.com/in/rickdenatale

--

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-us...@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.


Reply via email to