From: Junio C Hamano <gitster@pobox.com>
Date: Wed, 27 Oct 2021 20:16:35 GMT
Subject: Re: [PATCH] Remove negation from the merge option "--no-verify"
Message-ID: <xmqq4k92w7do.fsf@gitster.g>
In-Reply-To: <YXlTpzrY7KFqRlno@pflmari>

Alex Riesen <alexander.riesen@cetitec.com> writes:

> From: Alex Riesen <raa.lkml@gmail.com>
>
> This allows re-enabling hooks disabled by an earlier "--no-verify"
> in command-line and makes the interface more consistent.
>
> Signed-off-by: Alex Riesen <raa.lkml@gmail.com>
>
> ---
>
> This one is on top of "[PATCH] Fix "commit-msg" hook unexpectedly called for
> "git pull --no-verify" (http://public-inbox.org/git/YXfwanz3MynCLDmn@pflmari/).
> Which is a bit awkward. Should I resend as series?

Don't we need to do this at the root cause command "git commit"?  It
is documented to take "--no-verify" but not "--verify" to countermand
an earlier "--no-verify" on the command line.

And yes, I agree that we shouldn't introduce an awkwardness in one
step of the series and fix it in another step of the same series.