From: Thomas Rast <trast@inf•ethz.ch>
To: Junio C Hamano <gitster@pobox•com>
Cc: Aaron Schrab <aaron@schrab•com>, <git@vger•kernel.org>
Subject: Re: [PATCH] Document push --no-verify
Date: Wed, 22 May 2013 22:23:59 +0200 [thread overview]
Message-ID: <87vc6arcf4.fsf@linux-k42r.v.cablecom.net> (raw)
In-Reply-To: <7vli77j5nm.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Wed, 22 May 2013 10:17:17 -0700")
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
next prev parent reply other threads:[~2013-05-22 20:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 9:23 [PATCH] Document push --no-verify Thomas Rast
2013-05-22 17:17 ` Junio C Hamano
2013-05-22 20:23 ` Thomas Rast [this message]
2013-05-23 13:34 ` [PATCH v2] " Thomas Rast
2013-05-23 14:37 ` Michael S. Tsirkin
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vc6arcf4.fsf@linux-k42r.v.cablecom.net \
--to=trast@inf$(echo .)ethz.ch \
--cc=aaron@schrab$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox