* David Malcolm: > +<p>The log message for a checkin should be a single line giving a > +descriptive title for the checkin, followed by a blank line, followed by > +the complete ChangeLog entry for the change. This is the git convention; > +giving titles to checkins makes life easier for developers using git > +mirrors of SVN. Typically the descriptive title should be the "Subject" > +line of the relevant gcc-patches thread (without any "[PATCH]" or "[PING]" > +prefixes).</p>
For glibc, we often try to put the reason for the change in the commit message. Especially for code deletions, you can't really add a comment to the sources, and official policy is that you must not put explanations into the ChangeLog file (it's just a mechanical description of the change). So giving an explanation *somewhere* is often nice, and the commit message is a good place for that.
