On Thu, Jul 4, 2013 at 3:42 PM, Antoine Pelisse <apeli...@gmail.com> wrote:
>>> Your problem is that your hook script is not checking $2 so it is
>>> overwriting the message even when you do not want to do so.
>> No, it isn't. Not by git-gui at least. Check /tmp/hook.log with the
>> hook I provided...
> So what you mean is that the hook is not executed with the correct parameters?
> Could you please provide the output of the /tmp/hook.log file (I can't
> reproduce right now) ?
It only runs for "New commit" (possibly with merge or squash as
arguments). In my case the log is:
Not running the hook for amend is another problem.
What I referred to was that handling the hook's result is done without
checking if the state has changed while it was running, like Fredrik
has already pointed out.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html