From: Josef Weidendorfer <Josef.Weidendorfer@gmx.de>
To: Wolfgang Denk <wd@denx.de>
Cc: Andreas Ericsson <ae@op5.se>, Petr Baudis <pasky@suse.cz>,
git@vger.kernel.org
Subject: Re: cg-commit does not run pre-commit hook?
Date: Thu, 12 Oct 2006 19:02:14 +0200 [thread overview]
Message-ID: <200610121902.14829.Josef.Weidendorfer@gmx.de> (raw)
In-Reply-To: <20061012155444.27391353BDE@atlas.denx.de>
On Thursday 12 October 2006 17:54, Wolfgang Denk wrote:
> Yes, but only *after* doing the job. That's why I'm looking for a
> pre-commit hook.
pre-commit is not good either, as it runs *before* the editor pops up.
So it can not access the commit message.
You ask for a "pre-commit-post-edit" hook, which AFAIK currently
is not available in git.
> 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).
Can't you create the Changelog directly before preparing such an
tarball?
Usually when making a release/snapshot for a typical project, you
can not directly take the newest tree from the SCM, but need
to generate some files (like configure with automake/autoconf).
Josef
>
>
> Best regards,
>
> Wolfgang Denk
>
prev parent reply other threads:[~2006-10-12 17:04 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
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 [this message]
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=200610121902.14829.Josef.Weidendorfer@gmx.de \
--to=josef.weidendorfer@gmx.de \
--cc=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
--cc=wd@denx.de \
/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).