Commit messages

Thomas Doerfler Thomas.Doerfler at
Tue Jan 24 09:53:31 UTC 2012


GIT has separate means to collect and maintain the information, which
changes are part of a patch. So this mechanical function of the
ChangeLogs is no longer needed. Nevertheless it is useful to see, which
patches were applied to the files, who applied them and which files were
also changed.

Those people having read access to the GIT Repo can query this
information online, but it may be sensible to collect that information
at one place for documentation purposes. And this is (IMHO) he main
purpose of a ChangeLog.

So wouldn't it be possibe to generate the Changelogs (maybe in a
slightly modified format) automatically now, based on the commit
messages and other info in the GIT repository?

It seems other projects also went that way. A quick google brought many
hits, e.g. (in random order):



Am 24.01.2012 10:32, schrieb Ralf Corsepius:
> On 01/24/2012 10:17 AM, Sebastian Huber wrote:
>> On 01/23/2012 11:08 PM, Joel Sherrill wrote:
>>> On 01/23/2012 02:31 AM, Sebastian Huber wrote:
>>>> Hello,
>>>> I think we should write down (or copy from somewhere else) some
>>>> standard for
>>>> the commit messages. How to format it and what to put in it. Maybe
>>>> also some
>>>> standard phrases.
>>> I was hoping someone else would post first but here is what I
>>> personally would like to see.
>>> I think ChangeLog's need to continue to exist. They are part
>>> of the GNU Coding Standard and useful to those getting releases.
>> I guess the GNU Coding Standard needs an update.
> Well, with all due respect, I think some people don't have sufficient
> experience to understand why the GCS says so.
> Ralf
> _______________________________________________
> rtems-devel mailing list
> rtems-devel at

embedded brains GmbH
Thomas Doerfler
Obere Lagerstrasse 30
D-82178 Puchheim
email: Thomas.Doerfler at
Phone: +49-89-18908079-2
Fax: +49-89-18908079-9
PGP: Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.

More information about the devel mailing list