From: John Feminella Date: 2011-06-13T23:37:43+09:00 Subject: Re: commit message conventions Agreed. Reference the ticket, which can hold all the data about what goal is ultimately satisfied by the commit. ~ jf -- John Feminella Principal Consultant, BitsBuilder LI: http://www.linkedin.com/in/johnxf SO: http://stackoverflow.com/users/75170/ On Mon, Jun 13, 2011 at 10:06, Michael Sokol wrote: > On Jun 13, 2011, at 9:55 AM, Intransition wrote: > >> On Jun 13, 9:13 am, brab...@gmail.com wrote: >> >>> git-commit(1) >>>     Though not required, it’s 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? >> > > I'm not exactly sure what kind of categorization you are talking about, is it concerning the group of users it affects? > > Most of the time, the ticket you reference to in your commit will be categorized and will hold lots of necessary information. > > Michael >