From: Thomas Rast <trast@inf.ethz.ch>
Date: Wed, 22 May 2013 20:23:59 GMT
Subject: Re: [PATCH] Document push --no-verify
Message-ID: <87vc6arcf4.fsf@linux-k42r.v.cablecom.net>
In-Reply-To: <7vli77j5nm.fsf@alter.siamese.dyndns.org>

Junio C Hamano <gitster@pobox.com> writes:

> Thomas Rast <trast@inf.ethz.ch> writes:
>
>> ec55559 (push: Add support for pre-push hooks, 2013-01-13) forgot to
>> add a note to git-push(1) about the new --no-verify option.
>
> Does it take --verify option (that may well be the default) so that
> somebody with
>
>          [alias] put = push --no-verify
>
> can say "git put --verify args..."?

Yes.  Doesn't parse-options implicitly do the correct negation for all
boolean options, even those that are declared in their negative form?

-- 
Thomas Rast
trast@{inf,student}.ethz.ch