[PATCH] push: document --no-verify

[PATCH] push: document --no-verify

[Michael S. Tsirkin]

commit ec55559f937727bcb0fa8a3dfe6af68c188e968a added
--no-verify flag to git push, but didn't document it.
It's a useful flag when using pre-push hooks so
add the documentation.

Suggested-by: Thomas Rast <trast@inf.ethz.ch>
Cc: Aaron Schrab <aaron@schrab.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
---
 Documentation/git-push.txt | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt
index d514813..346b28a 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
 -----------
@@ -162,6 +162,11 @@ useful if you write an alias or script around 'git push'.
 	linkgit:git-pull[1] and other commands. For more information,
 	see 'branch.<name>.merge' in linkgit:git-config[1].
 
+-n::
+--no-verify::
+	This option bypasses the pre-commit and commit-msg hooks.
+	See also linkgit:githooks[5].
+
 --[no-]thin::
 	These options are passed to linkgit:git-send-pack[1]. A thin transfer
 	significantly reduces the amount of sent data when the sender and
-- 
MST

Re: [PATCH] push: document --no-verify

[Thomas Rast]

"Michael S. Tsirkin" <mst@redhat.com> writes:

> commit ec55559f937727bcb0fa8a3dfe6af68c188e968a added
> --no-verify flag to git push, but didn't document it.
> It's a useful flag when using pre-push hooks so
> add the documentation.
>
> Suggested-by: Thomas Rast <trast@inf.ethz.ch>
> Cc: Aaron Schrab <aaron@schrab.com>
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
[...]
> +-n::
> +--no-verify::
> +	This option bypasses the pre-commit and commit-msg hooks.
> +	See also linkgit:githooks[5].
> +

Umm, half of that is not correct :-)

Push doesn't have the -n short form that git-commit does, and the hook
names are wrong.

I also ended up writing a patch myself; sorry for not telling you on
IRC:

  http://thread.gmane.org/gmane.comp.version-control.git/225141

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

Re: [PATCH] push: document --no-verify

[Michael S. Tsirkin]

On Wed, May 22, 2013 at 02:12:21PM +0200, Thomas Rast wrote:
> "Michael S. Tsirkin" <mst@redhat.com> writes:
> 
> > commit ec55559f937727bcb0fa8a3dfe6af68c188e968a added
> > --no-verify flag to git push, but didn't document it.
> > It's a useful flag when using pre-push hooks so
> > add the documentation.
> >
> > Suggested-by: Thomas Rast <trast@inf.ethz.ch>
> > Cc: Aaron Schrab <aaron@schrab.com>
> > Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> [...]
> > +-n::
> > +--no-verify::
> > +	This option bypasses the pre-commit and commit-msg hooks.
> > +	See also linkgit:githooks[5].
> > +
> 
> Umm, half of that is not correct :-)
> 
> Push doesn't have the -n short form that git-commit does,

Hmm true - in fact -n means dry-run.

> and the hook
> names are wrong.
> 
> I also ended up writing a patch myself; sorry for not telling you on
> IRC:
> 
>   http://thread.gmane.org/gmane.comp.version-control.git/225141

Great, thanks.

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