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

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

From
Thomas Rast <trast@inf.ethz.ch>
Date
May 22, 2013, 20:23 UTC
Message-ID
<87vc6arcf4.fsf@linux-k42r.v.cablecom.net>
In-Reply-To
<7vli77j5nm.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> writes:
Show 11 quoted lines
> Thomas Rast <trast@inf.ethz.ch> writes:
>
>> 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.
>
> Does it take --verify option (that may well be the default) so that
> somebody with
>
>          [alias] put = push --no-verify
>
> can say "git put --verify args..."?

Yes. Doesn't parse-options implicitly do the correct negation for all boolean options, even those that are declared in their negative form?

-- 
Thomas Rast
trast@{inf,student}.ethz.ch
Previous: Junio C HamanoNext: Thomas Rast
Message 3 of 5 in “Document push --no-verify”
  1. Document push --no-verifyThomas Rast, May 22, 2013
  2. Junio C HamanoMay 22, 2013
  3. Thomas RastMay 22, 2013
  4. Document push --no-verifyThomas Rast, May 23, 2013
  5. Michael S. TsirkinMay 23, 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.