From: Michael S. Tsirkin Date: Wed, 22 May 2013 10:43:56 GMT Subject: [PATCH] push: document --no-verify Message-ID: <20130522104356.GA5472@redhat.com> 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 Cc: Aaron Schrab Signed-off-by: Michael S. Tsirkin --- 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=] [--repo=] [-f | --force] [--prune] [-v | --verbose] [-u | --set-upstream] - [ [...]] + [--no-verify] [ [...]] 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..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