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: [PATCH] Document push --no-verify
Date: Wed, 22 May 2013 11:23:08 +0200 [thread overview]
Message-ID: <bac9440ba0c977f6bd4207ac423f82b716947cc0.1369214470.git.trast@inf.ethz.ch> (raw)
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.
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[]
--
1.8.3.rc3.490.g2f233b5
next reply other threads:[~2013-05-22 9:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 9:23 Thomas Rast [this message]
2013-05-22 17:17 ` [PATCH] Document push --no-verify Junio C Hamano
2013-05-22 20:23 ` Thomas Rast
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=bac9440ba0c977f6bd4207ac423f82b716947cc0.1369214470.git.trast@inf.ethz.ch \
--to=trast@inf.ethz.ch \
--cc=aaron@schrab.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).