On 06/13/2011 06:55 AM, Intransition wrote:
> On Jun 13, 9:13 am, brab... / gmail.com wrote:
>
>> git-commit(1)
>>      Though not required, itÃÔ a good idea to begin the commit
>>      message with a single short (less than 50 character) line
>>      summarizing the change, followed by a blank line and then a
>>      more thorough description. Tools that turn commits into email,
>>      for example, use the first line on the Subject: line and the rest
>>      of the commit in the body.
> But what about a categorizing a commit?

For projects that have a few parts, I've started using "[Category] blah 
blah blah..." for the first line. Like, "[Parser] Fixed whatever parser 
bug". Makes it easy to scan through the commits and know which are 
relevant, and sometimes allows the commit message to be shorter by 
providing compact context.

-Justin