git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: Petr Baudis <pasky@suse.cz>
Cc: git@vger.kernel.org
Subject: Re: cg-commit does not run pre-commit hook?
Date: Thu, 12 Oct 2006 16:27:36 +0200	[thread overview]
Message-ID: <20061012142736.74DE7353BDE@atlas.denx.de> (raw)
In-Reply-To: Your message of "Thu, 12 Oct 2006 03:15:48 +0200." <20061012011548.GT20017@pasky.or.cz>

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? 

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
The goal of science is to build better mousetraps. The goal of nature
is to build better mice.

  reply	other threads:[~2006-10-12 14:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-11 20:30 cg-commit does not run pre-commit hook? Wolfgang Denk
2006-10-12  1:15 ` Petr Baudis
2006-10-12 14:27   ` Wolfgang Denk [this message]
2006-10-12 14:42     ` Andreas Ericsson
2006-10-12 15:54       ` Wolfgang Denk
2006-10-12 16:59         ` Linus Torvalds
2006-10-12 17:20           ` Linus Torvalds
2006-10-12 17:02         ` Josef Weidendorfer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20061012142736.74DE7353BDE@atlas.denx.de \
    --to=wd@denx.de \
    --cc=git@vger.kernel.org \
    --cc=pasky@suse.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).