[Insight-developers] Commit message prefixes

[Bill Lorensen]

The idea is to allow a human to scan them quickly. 1 character
abbreviations don't help.

I'm still searching for the mailing list discussion.

On Fri, Oct 29, 2010 at 2:21 PM, David Doria <daviddoria at gmail.com> wrote:
> On Fri, Oct 29, 2010 at 2:14 PM, Stephen Aylward
> <stephen.aylward at kitware.com> wrote:
>>
>> Ok,
>>
>> I thought we had decided on ITK to use them many many years ago, and I
>> hadn't heard of a discussion to change.   Perhaps it was the VTK
>> folks.
>>
>> We did previously have hooks for these, right?
>>
>> Those 4-5 characters provide critical info.   If anything, we should
>> welcome them for the space and time they do save for those creating
>> the messages as well as those reading them.   They embody all things
>> good about shorthand, codes, keys, names, IDs, stereotypes, labels,
>> acronyms, and abbrevs. in a simple, universally accepted package that
>> only requires 4-5 characters per usage :)
>>
>> s
>
> I'm not sure how many prefixes there are, but the ones I know are BUG,
> STYLE, and ENH. If character count is the only concern, could they be
> shortened to B:, S:, and E: ? I vote +1 for mandatory prefixes.
> David