From: Jonas Fonseca <fonseca@diku.dk>
To: Jim Meyering <jim@meyering.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] cg-commit: Fix a typo that would inhibit running of post-commit script:
Date: Fri, 25 Aug 2006 02:20:13 +0200 [thread overview]
Message-ID: <20060825002013.GG2817@diku.dk> (raw)
In-Reply-To: <8764giro6t.fsf@rho.meyering.net>
Jim Meyering <jim@meyering.net> wrote Thu, Aug 24, 2006:
> I tried cg-commit with a commit hook, but the hook never ran.
> The problem was a typo:
>
> Fix a typo that would inhibit running the post-commit script:
> s/commit-post/post-commit/.
If I remember correctly, historically, the commit-post existed before
the post-commit appeared. You can see that it is documented in the man
page so it is not a typo.
However, this should certainly be updated, but I think a better fix
would be to transitionally warn the user about the existence of the
commit-post hook before using it in favour of post-commit.
> diff --git a/cg-commit b/cg-commit
> index 9d3b1a1..82eea60 100755
> --- a/cg-commit
> +++ b/cg-commit
> @@ -604,15 +604,16 @@ if [ "$newhead" ]; then
> branchname="$(cat "$_git/branch-name")"
> fi
> [ -z "$branchname" ] && [ "$_git_head" != "master" ] && branchname="$_git_head"
> - if [ -x "$_git/hooks/post-commit" -a ! "$no_hooks" ]; then
> + post_commit="$_git/hooks/post-commit"
> + if [ -x "$post_commit" -a ! "$no_hooks" ]; then
> if [ "$(git-repo-config --bool cogito.hooks.commit.post.allmerged)" = "true" ]; then
> # We just hope that for the initial commit, the user didn't
> # manage to install the hook yet.
> for merged in $(git-rev-list $newhead ^$oldhead | tac); do
> - "$_git/hooks/post-commit" "$merged" "$branchname"
> + "$post_commit" "$merged" "$branchname"
> done
> else
> - "$_git/hooks/post-commit" "$newhead" "$branchname"
> + "$post_commit" "$newhead" "$branchname"
> fi
> fi
The patch looks more like a refactoring of a previous commit that did
the commit-post -> post-commit replacement.
--
Jonas Fonseca
next prev parent reply other threads:[~2006-08-25 0:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-24 18:19 [PATCH] cg-commit: Fix a typo that would inhibit running of post-commit script: Jim Meyering
2006-08-25 0:20 ` Jonas Fonseca [this message]
2006-09-16 15:10 ` Jim Meyering
2006-09-24 17:39 ` Petr Baudis
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=20060825002013.GG2817@diku.dk \
--to=fonseca@diku.dk \
--cc=git@vger.kernel.org \
--cc=jim@meyering.net \
/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).