From: Junio C Hamano <gitster@pobox.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: git@vger.kernel.org, Phillip Wood <phillip.wood@dunelm.org.uk>
Subject: Re: prepare-commit-msg hook no longer run for cherry-pick?
Date: Wed, 10 Jan 2018 13:14:23 -0800 [thread overview]
Message-ID: <xmqq373d1knk.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CAKdAkRSuNhEri+3eUbX8iVjr0JUyADSJBtgL==VjNwgKwe3Xqw@mail.gmail.com> (Dmitry Torokhov's message of "Wed, 10 Jan 2018 11:25:59 -0800")
Dmitry Torokhov <dmitry.torokhov@gmail.com> writes:
> Right, so it looks like the master works well, it is next(?) branch
> that is troublesome (apparently we pack experimental internally?).
>
> I bisected it down to:
>
> commit 356ee4659bb551cd9464b317d691827276752c2d (refs/bisect/bad)
> Author: Phillip Wood <phillip.wood@dunelm.org.uk>
> Date: Fri Nov 24 11:07:57 2017 +0000
>
> sequencer: try to commit without forking 'git commit'
> ...
>
> With this commit the hook is not being run unless I specify '-e' flag
> to cherry-pick.
Thanks.
next prev parent reply other threads:[~2018-01-10 21:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-05 18:48 prepare-commit-msg hook no longer run for cherry-pick? Dmitry Torokhov
2018-01-10 0:39 ` Dmitry Torokhov
2018-01-10 2:24 ` Junio C Hamano
2018-01-10 19:25 ` Dmitry Torokhov
2018-01-10 21:14 ` Junio C Hamano [this message]
2018-01-19 14:19 ` [PATCH 0/2] sequencer: run 'prepare-commit-msg' hook Phillip Wood
2018-01-19 14:19 ` [PATCH 1/2] t7505: Add tests for cherry-pick and rebase -i/-p Phillip Wood
2018-01-20 0:48 ` Eric Sunshine
2018-01-19 14:19 ` [PATCH 2/2] sequencer: run 'prepare-commit-msg' hook Phillip Wood
2018-01-23 10:24 ` [PATCH v2 0/2] sequencer: run 'prepare-commit-msg' hook Phillip Wood
2018-01-23 10:24 ` [PATCH v2 1/2] t7505: Add tests for cherry-pick and rebase -i/-p Phillip Wood
2018-01-23 18:41 ` Junio C Hamano
2018-01-23 18:41 ` Junio C Hamano
2018-01-23 10:24 ` [PATCH v2 2/2] sequencer: run 'prepare-commit-msg' hook Phillip Wood
2018-01-24 12:34 ` [PATCH v3 0/3] " Phillip Wood
2018-01-24 12:34 ` [PATCH v3 1/3] t7505: style fixes Phillip Wood
2018-01-24 12:34 ` [PATCH v3 2/3] t7505: Add tests for cherry-pick and rebase -i/-p Phillip Wood
2018-01-24 18:39 ` Eric Sunshine
2018-01-24 12:34 ` [PATCH v3 3/3] sequencer: run 'prepare-commit-msg' hook Phillip Wood
2018-01-24 18:51 ` Ramsay Jones
2018-01-24 18:59 ` Junio C Hamano
2018-01-25 16:33 ` Phillip Wood
2018-01-29 23:06 ` Johannes Schindelin
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq373d1knk.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=dmitry.torokhov@gmail.com \
--cc=git@vger.kernel.org \
--cc=phillip.wood@dunelm.org.uk \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).