Commit messages

[Gedare Bloom]

On Tue, Feb 21, 2012 at 1:02 PM, Ralf Corsepius
<ralf.corsepius at rtems.org> wrote:
> On 02/21/2012 04:38 PM, Sebastian Huber wrote:
>>
>> My intention was to give the Git commit messages a standard format. This
>> topic is not about ChangeLog files.
>>
> I really do not care about git's internal changelog messages, because they
> are internal implementation details
>
if we determine a standard for git commit messages then maybe we can
use commit messages to generate ChangeLog entries. We could, for
example, have a standard way to flag a commit message as one that
should be used to generate a ChangeLog entry. Or we might require that
devs provide a useful ChangeLog message when merging a branch
containing the changes. We can ignore all the intermediate commits if
we have one over-arching message that can be used to describe all of
the changes in the merge. This should help users determine what has
changed and why, and probably is more maintainable than our existing
manual ad-hoc process.

-Gedare