{"thread":{"id":"33896","subject":"[PATCH] Document push --no-verify","startedAt":"2013-05-22T09:23:08Z","lastAt":"2013-05-23T14:37:11Z","messageCount":5,"participants":["Thomas Rast","Junio C Hamano","Michael S. Tsirkin"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"218158","messageId":"bac9440ba0c977f6bd4207ac423f82b716947cc0.1369214470.git.trast@inf.ethz.ch","threadId":"33896","inReplyTo":null,"subject":"[PATCH] Document push --no-verify","fromName":"Thomas Rast","fromEmail":"trast@inf.ethz.ch","sentAt":"2013-05-22T09:23:08Z","receivedAt":"2013-05-22T09:23:08Z","isPatch":true,"sender":{"key":"tr@thomasrast.ch","avatar":"https://avatars.githubusercontent.com/u/153510?v=4"},"body":"ec55559 (push: Add support for pre-push hooks, 2013-01-13) forgot to\nadd a note to git-push(1) about the new --no-verify option.\n\nSigned-off-by: Thomas Rast <trast@inf.ethz.ch>\n---\n\nThe insertion spot is at the end, because the existing ordering is\nindistinguishable from random.  This should also be fixed, but is a\nmuch bigger change and probably not suitable for an -rc period.\n\n\n Documentation/git-push.txt | 5 ++++-\n 1 file changed, 4 insertions(+), 1 deletion(-)\n\ndiff --git a/Documentation/git-push.txt b/Documentation/git-push.txt\nindex d514813..426b3d2 100644\n--- a/Documentation/git-push.txt\n+++ b/Documentation/git-push.txt\n@@ -11,7 +11,7 @@ SYNOPSIS\n [verse]\n 'git push' [--all | --mirror | --tags] [--follow-tags] [-n | --dry-run] [--receive-pack=<git-receive-pack>]\n \t   [--repo=<repository>] [-f | --force] [--prune] [-v | --verbose] [-u | --set-upstream]\n-\t   [<repository> [<refspec>...]]\n+\t   [--no-verify] [<repository> [<refspec>...]]\n \n DESCRIPTION\n -----------\n@@ -195,6 +195,9 @@ useful if you write an alias or script around 'git push'.\n \tbe pushed. If on-demand was not able to push all necessary\n \trevisions it will also be aborted and exit with non-zero status.\n \n+--no-verify::\n+\tBypass the pre-push hook (see linkgit:githooks[5]).\n+\n \n include::urls-remotes.txt[]\n \n-- \n1.8.3.rc3.490.g2f233b5\n"},{"id":"218194","messageId":"7vli77j5nm.fsf@alter.siamese.dyndns.org","threadId":"33896","inReplyTo":"bac9440ba0c977f6bd4207ac423f82b716947cc0.1369214470.git.trast@inf.ethz.ch","subject":"Re: [PATCH] Document push --no-verify","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2013-05-22T17:17:17Z","receivedAt":"2013-05-22T17:17:17Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Thomas Rast <trast@inf.ethz.ch> writes:\n\n> ec55559 (push: Add support for pre-push hooks, 2013-01-13) forgot to\n> add a note to git-push(1) about the new --no-verify option.\n\nDoes it take --verify option (that may well be the default) so that\nsomebody with\n\n         [alias] put = push --no-verify\n\ncan say \"git put --verify args...\"?\n\n>\n> Signed-off-by: Thomas Rast <trast@inf.ethz.ch>\n> ---\n>\n> The insertion spot is at the end, because the existing ordering is\n> indistinguishable from random.  This should also be fixed, but is a\n> much bigger change and probably not suitable for an -rc period.\n>\n>\n>  Documentation/git-push.txt | 5 ++++-\n>  1 file changed, 4 insertions(+), 1 deletion(-)\n>\n> diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt\n> index d514813..426b3d2 100644\n> --- a/Documentation/git-push.txt\n> +++ b/Documentation/git-push.txt\n> @@ -11,7 +11,7 @@ SYNOPSIS\n>  [verse]\n>  'git push' [--all | --mirror | --tags] [--follow-tags] [-n | --dry-run] [--receive-pack=<git-receive-pack>]\n>  \t   [--repo=<repository>] [-f | --force] [--prune] [-v | --verbose] [-u | --set-upstream]\n> -\t   [<repository> [<refspec>...]]\n> +\t   [--no-verify] [<repository> [<refspec>...]]\n>  \n>  DESCRIPTION\n>  -----------\n> @@ -195,6 +195,9 @@ useful if you write an alias or script around 'git push'.\n>  \tbe pushed. If on-demand was not able to push all necessary\n>  \trevisions it will also be aborted and exit with non-zero status.\n>  \n> +--no-verify::\n> +\tBypass the pre-push hook (see linkgit:githooks[5]).\n> +\n>  \n>  include::urls-remotes.txt[]\n"},{"id":"218207","messageId":"87vc6arcf4.fsf@linux-k42r.v.cablecom.net","threadId":"33896","inReplyTo":"7vli77j5nm.fsf@alter.siamese.dyndns.org","subject":"Re: [PATCH] Document push --no-verify","fromName":"Thomas Rast","fromEmail":"trast@inf.ethz.ch","sentAt":"2013-05-22T20:23:59Z","receivedAt":"2013-05-22T20:23:59Z","isPatch":true,"sender":{"key":"tr@thomasrast.ch","avatar":"https://avatars.githubusercontent.com/u/153510?v=4"},"body":"Junio C Hamano <gitster@pobox.com> writes:\n\n> Thomas Rast <trast@inf.ethz.ch> writes:\n>\n>> ec55559 (push: Add support for pre-push hooks, 2013-01-13) forgot to\n>> add a note to git-push(1) about the new --no-verify option.\n>\n> Does it take --verify option (that may well be the default) so that\n> somebody with\n>\n>          [alias] put = push --no-verify\n>\n> can say \"git put --verify args...\"?\n\nYes.  Doesn't parse-options implicitly do the correct negation for all\nboolean options, even those that are declared in their negative form?\n\n-- \nThomas Rast\ntrast@{inf,student}.ethz.ch\n"},{"id":"218261","messageId":"ba24ea6f9fedc05690ee93a805d4f468650a942c.1369315855.git.trast@inf.ethz.ch","threadId":"33896","inReplyTo":"87vc6arcf4.fsf@linux-k42r.v.cablecom.net","subject":"[PATCH v2] Document push --no-verify","fromName":"Thomas Rast","fromEmail":"trast@inf.ethz.ch","sentAt":"2013-05-23T13:34:11Z","receivedAt":"2013-05-23T13:34:11Z","isPatch":true,"sender":{"key":"tr@thomasrast.ch","avatar":"https://avatars.githubusercontent.com/u/153510?v=4"},"body":"ec55559 (push: Add support for pre-push hooks, 2013-01-13) forgot to\nadd a note to git-push(1) about the new --no-verify option.\n\nSigned-off-by: Thomas Rast <trast@inf.ethz.ch>\n---\n\nJunio replied privately that it should also mention the --verify\npossibility.\n\nSo why not.  But this needs to be fixed across the board eventually;\n0f1930c (parse-options: allow positivation of options starting, with\nno-, 2012-02-25) did not update any docs, so none of the other --no-\noptions mention their positive forms.\n\n\n Documentation/git-push.txt | 7 ++++++-\n 1 file changed, 6 insertions(+), 1 deletion(-)\n\ndiff --git a/Documentation/git-push.txt b/Documentation/git-push.txt\nindex d514813..df5be26 100644\n--- a/Documentation/git-push.txt\n+++ b/Documentation/git-push.txt\n@@ -11,7 +11,7 @@ SYNOPSIS\n [verse]\n 'git push' [--all | --mirror | --tags] [--follow-tags] [-n | --dry-run] [--receive-pack=<git-receive-pack>]\n \t   [--repo=<repository>] [-f | --force] [--prune] [-v | --verbose] [-u | --set-upstream]\n-\t   [<repository> [<refspec>...]]\n+\t   [--no-verify] [<repository> [<refspec>...]]\n \n DESCRIPTION\n -----------\n@@ -195,6 +195,11 @@ useful if you write an alias or script around 'git push'.\n \tbe pushed. If on-demand was not able to push all necessary\n \trevisions it will also be aborted and exit with non-zero status.\n \n+--[no-]verify::\n+\tToggle the pre-push hook (see linkgit:githooks[5]).  The\n+\tdefault is \\--verify, giving the hook a chance to prevent the\n+\tpush.  With \\--no-verify, the hook is bypassed completely.\n+\n \n include::urls-remotes.txt[]\n \n-- \n1.8.3.rc3.486.gfe16094\n"},{"id":"218265","messageId":"20130523143711.GA24037@redhat.com","threadId":"33896","inReplyTo":"ba24ea6f9fedc05690ee93a805d4f468650a942c.1369315855.git.trast@inf.ethz.ch","subject":"Re: [PATCH v2] Document push --no-verify","fromName":"Michael S. Tsirkin","fromEmail":"mst@redhat.com","sentAt":"2013-05-23T14:37:11Z","receivedAt":"2013-05-23T14:37:11Z","isPatch":true,"sender":{"key":"mst@kernel.org","avatar":null},"body":"On Thu, May 23, 2013 at 03:34:11PM +0200, Thomas Rast wrote:\n> ec55559 (push: Add support for pre-push hooks, 2013-01-13) forgot to\n> add a note to git-push(1) about the new --no-verify option.\n> \n> Signed-off-by: Thomas Rast <trast@inf.ethz.ch>\n\n\nThanks. FWIW\n\nReviewed-by: Michael S. Tsirkin <mst@redhat.com>\n\n> ---\n> \n> Junio replied privately that it should also mention the --verify\n> possibility.\n> \n> So why not.  But this needs to be fixed across the board eventually;\n> 0f1930c (parse-options: allow positivation of options starting, with\n> no-, 2012-02-25) did not update any docs, so none of the other --no-\n> options mention their positive forms.\n> \n> \n>  Documentation/git-push.txt | 7 ++++++-\n>  1 file changed, 6 insertions(+), 1 deletion(-)\n> \n> diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt\n> index d514813..df5be26 100644\n> --- a/Documentation/git-push.txt\n> +++ b/Documentation/git-push.txt\n> @@ -11,7 +11,7 @@ SYNOPSIS\n>  [verse]\n>  'git push' [--all | --mirror | --tags] [--follow-tags] [-n | --dry-run] [--receive-pack=<git-receive-pack>]\n>  \t   [--repo=<repository>] [-f | --force] [--prune] [-v | --verbose] [-u | --set-upstream]\n> -\t   [<repository> [<refspec>...]]\n> +\t   [--no-verify] [<repository> [<refspec>...]]\n>  \n>  DESCRIPTION\n>  -----------\n> @@ -195,6 +195,11 @@ useful if you write an alias or script around 'git push'.\n>  \tbe pushed. If on-demand was not able to push all necessary\n>  \trevisions it will also be aborted and exit with non-zero status.\n>  \n> +--[no-]verify::\n> +\tToggle the pre-push hook (see linkgit:githooks[5]).  The\n> +\tdefault is \\--verify, giving the hook a chance to prevent the\n> +\tpush.  With \\--no-verify, the hook is bypassed completely.\n> +\n>  \n>  include::urls-remotes.txt[]\n>  \n> -- \n> 1.8.3.rc3.486.gfe16094\n"}]}