From: Junio C Hamano <gitster@pobox.com>
Date: Wed, 22 May 2013 17:17:17 GMT
Subject: Re: [PATCH] Document push --no-verify
Message-ID: <7vli77j5nm.fsf@alter.siamese.dyndns.org>
In-Reply-To: <bac9440ba0c977f6bd4207ac423f82b716947cc0.1369214470.git.trast@inf.ethz.ch>

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..."?

>
> Signed-off-by: Thomas Rast <trast@inf.ethz.ch>
> ---
>
> The insertion spot is at the end, because the existing ordering is
> indistinguishable from random.  This should also be fixed, but is a
> much bigger change and probably not suitable for an -rc period.
>
>
>  Documentation/git-push.txt | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt
> index d514813..426b3d2 100644
> --- a/Documentation/git-push.txt
> +++ b/Documentation/git-push.txt
> @@ -11,7 +11,7 @@ SYNOPSIS
>  [verse]
>  'git push' [--all | --mirror | --tags] [--follow-tags] [-n | --dry-run] [--receive-pack=<git-receive-pack>]
>  	   [--repo=<repository>] [-f | --force] [--prune] [-v | --verbose] [-u | --set-upstream]
> -	   [<repository> [<refspec>...]]
> +	   [--no-verify] [<repository> [<refspec>...]]
>  
>  DESCRIPTION
>  -----------
> @@ -195,6 +195,9 @@ useful if you write an alias or script around 'git push'.
>  	be pushed. If on-demand was not able to push all necessary
>  	revisions it will also be aborted and exit with non-zero status.
>  
> +--no-verify::
> +	Bypass the pre-push hook (see linkgit:githooks[5]).
> +
>  
>  include::urls-remotes.txt[]