Re: cg-commit does not run pre-commit hook?

From: Andreas Ericsson <ae@op5.se>
Date: Oct 12, 2006, 14:42 UTC
Message-ID: <452E545F.6060406@op5.se>
In-Reply-To: <20061012142736.74DE7353BDE@atlas.denx.de>

Wolfgang Denk wrote:

Show 19 quoted lines

> Dear Petr,
> 
> in message <20061012011548.GT20017@pasky.or.cz> you wrote:
>>   historically, Git and Cogito use a different set of hooks (Cogito got
>> hooks first but Git picked own names and usage and now is prevalent).
> 
> I see. And current versions of cogito don't support any pre-commit
> script, right?
> 
>> I have plans for making Cogito support Git hooks and slowly deprecate
>> those own ones for which Git has counterparts, but didn't get to it yet.
>> I might do today during the more boring lectures... ;-)
> 
> Keeping my fingers crossed :-)
> 
> 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

The commit message is already saved and git (and cogito, I presume) provide tools to fetch those messages in the relevant different orders (although ordering by date is flakey sometimes; see list-archives for discussion).

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.

That aside, for actual releases, I generally write a short, gisted "what's new" thingie inside the tag, based on the shortlog output and my own memory. This comes in handy when management wants to have their version of the shortlog, and developers can pretty easily find new features by just sifting through the tag-messages.

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231