Re: Nonempty second line in commit message (??)

[Ivan Shmakov]

>>>>> Jan D <address@hidden> writes:

 > While commiting I got this error:

 > "Nonempty second line in commit message".

 > Why can't the second line be non-empty?  Are commit message limitied
 > to one line now?  Or must the second be empty and then the rest be
 > non-empty?

        Yes.

        The first line is reserved for the summary, which should be a
        /concise/ overall description of the change.  For one thing, it
        should deliver the essence of the change even if you’re reading
        through emacs-diffs@ /and/ the messages there are listed
        one-per-line (assuming the 80 CPL IBM standard.)

        Naturally, such summary should never be long enough to warrant a
        second (or third, or…) line.

        The summary forms a paragraph on its own, so the usual
        ChangeLog-style details should follow after a customary
        “paragraph break” empty line.

 > Or is the error message just extraordinary bad?

-- 
FSF associate member #7257  http://boycottsystemd.org/  … 3013 B6A0 230E 334A