Re: [lmi] 72 chars for git log messages [Was: Improved input-sequence editor]

[Greg Chicares]

On 2016-05-29 22:36, Vadim Zeitlin wrote:
[...]
> GC> BTW, I'm going to add a number in square brackets to the first line of
> GC> any commit message that changes the defect count that 'test_coding_rules'
> GC> reports.
> 
>  Could we please document this somewhere?

It's documented in 'ChangeLog':

|     ...Whenever a defect is
|     corrected, write "Fix defect introduced YYYYMMDDTHHMMZ." as the
|     first sentence, and ponder the questions in 'DefectLog'; write up
|     any serious defect in that file.
...
| Run 'make check_concinnity' before
| committing to cvs: it identifies common problems such as incorrect
| copyright statements, and reports the "Number of marked defects" shown
| as [defect-count] above.

Someday I'll write something more comprehensive in a more obvious place.
Meanwhile, I don't mind making adjustments myself--for example, there are
RCS IDs in 'ce_skin_name.?pp' because you followed the lmi convention in
effect at the time you submitted the patches to add those files, and it's
no problem for me to remove them.