Dear Andreas, in message <452E545F.6060406@xxxxxx> you wrote: > > > I'm looking for a way to register the commit message into some > > changelog file which gets checked in with the same commit. Or is > > there another way to do this? > > git log Sorry, this does not work, as I can access the commit message only *after* the commit completed, and then it's too late to get it into a file that shall be included with the very same commit. > The commit message is already saved and git (and cogito, I presume) > provide tools to fetch those messages in the relevant different orders Yes, but only *after* doing the job. That's why I'm looking for a pre-commit hook. > One part of why a proper SCM is so good to use is that you shouldn't > have to maintain a separate changelog. The SCM should create one for you > when you ask it, based on the comments you've entered when actually > making the changes. True, as long as you can work within the SCM. The changelog file I'm talking about is mostly for people who just work with exported trees (for example, when they download a tarball). Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@xxxxxxx Everyting looks interesting until you do it. Then you find it's just another job. - Terry Pratchett, _Moving Pictures_ - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html