git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Thomas Rast <trast@inf.ethz.ch>
Date
May 22, 2013, 12:12 UTC
Message-ID
<878v378b8a.fsf@linux-k42r.v.cablecom.net>
In-Reply-To
<20130522104356.GA5472@redhat.com>
"Michael S. Tsirkin" <mst@redhat.com> writes:
Show 8 quoted lines
> 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>
[...]
Show 5 quoted lines
> +-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
Previous: Michael S. TsirkinNext: Michael S. Tsirkin
Message 2 of 3 in “push: document --no-verify”
  1. push: document --no-verifyMichael S. Tsirkin, May 22, 2013
  2. Thomas RastMay 22, 2013
  3. Michael S. TsirkinMay 22, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.