git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] merge: Honor prepare-commit-msg return code

From
Antoine Pelisse <apelisse@gmail.com>
Date
Jan 2, 2013, 21:02 UTC
Message-ID
<CALWbr2wWjwUnHFq1icMRuW=vjQDhTO1e_chffqUvDWY5za1Kiw@mail.gmail.com>
In-Reply-To
<7v623f2uam.fsf@alter.siamese.dyndns.org>
Show 5 quoted lines
>> prepare-commit-msg hook is run when committing to prepare the log
>> message. If the exit-status is non-zero, the commit should be aborted.
>
> I was scratching my head why you CC'ed Jay, until I dug up 65969d4
> (merge: honor prepare-commit-msg hook, 2011-02-14).
I did as suggested in "SubmittingPatches" :)
Show 9 quoted lines
>> +test_expect_success 'with failing hook (merge)' '
>> +
>> +     git checkout -B other HEAD@{1} &&
>> +     echo "more" >> file &&
>> +     git add file &&
>> +     chmod -x $HOOK &&
>
> I have a feeling that this will break folks without POSIXPERM
> prerequisite.

It felt wrong when I did it, but kept it consistent within the file. It indeed looks older than other test files I've seen so far but I don't feel like I know the test general-style-and-policy enough to fix it myself either.

Show 20 quoted lines
> diff --git a/t/t7505-prepare-commit-msg-hook.sh b/t/t7505-prepare-commit-msg-hook.sh
> index bc497bc..3573751 100755
> --- a/t/t7505-prepare-commit-msg-hook.sh
> +++ b/t/t7505-prepare-commit-msg-hook.sh
> @@ -172,11 +172,12 @@ test_expect_success 'with failing hook (merge)' '
>         git checkout -B other HEAD@{1} &&
>         echo "more" >> file &&
>         git add file &&
> -       chmod -x $HOOK &&
> +       rm -f "$HOOK" &&
>         git commit -m other &&
> -       chmod +x $HOOK &&
> +       write_script "$HOOK" <<-EOF
> +       exit 1
> +       EOF
>         git checkout - &&
> -       head=`git rev-parse HEAD` &&
>         test_must_fail git merge other
>
>  '

What about moving the hook file then ? Not very important to me, just a suggestion as it would keep the shebang.

Cheers,
Previous: Junio C HamanoNext: Junio C Hamano
Message 4 of 6 in “merge: Honor prepare-commit-msg return code”
  1. merge: Honor prepare-commit-msg return codeAntoine Pelisse, Jan 2, 2013
  2. Antoine PelisseJan 2, 2013
  3. Junio C HamanoJan 2, 2013
  4. Antoine PelisseJan 2, 2013
  5. Junio C HamanoJan 2, 2013
  6. Antoine PelisseJan 3, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.