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

[PATCH] rebase: Document --no-verify option to bypass pre-rebase hook

From
Nanako Shiraishi <nanako3@lavabit.com>
Date
Oct 13, 2008, 23:17 UTC
Message-ID
<20081014081716.6117@nanako3.lavabit.com>
In-Reply-To
<20081012212543.GG4856@spearce.org>
Signed-off-by: Nanako Shiraishi <nanako3@lavabit.com>
---
"Shawn O. Pearce" <spearce@spearce.org> writes:
Show 5 quoted lines
> * ns/rebase-noverify (Mon Oct 6 14:14:29 2008 +0900) 1 commit
>  + rebase --no-verify
>
> This adds --no-verify to git rebase, to avoid the pre-rebase hook.
> Lacks documentation but otherwise looks sound.
Here it is.
 Documentation/git-rebase.txt |    5 ++++-
 1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/Documentation/git-rebase.txt b/Documentation/git-rebase.txt
index 32f0f12..4e84380 100644
--- a/Documentation/git-rebase.txt
+++ b/Documentation/git-rebase.txt
@@ -9,7 +9,7 @@ SYNOPSIS
 --------
 [verse]
 'git rebase' [-i | --interactive] [-v | --verbose] [-m | --merge]
-	[-s <strategy> | --strategy=<strategy>]
+	[-s <strategy> | --strategy=<strategy>] [--no-verify]
 	[-C<n>] [ --whitespace=<option>] [-p | --preserve-merges]
 	[--onto <newbase>] <upstream> [<branch>]
 'git rebase' --continue | --skip | --abort
@@ -232,6 +232,9 @@ OPTIONS
 --verbose::
 	Display a diffstat of what changed upstream since the last rebase.
 
+--no-verify::
+	This option bypasses the pre-rebase hook.  See also linkgit:githooks[5].
+
 -C<n>::
 	Ensure at least <n> lines of surrounding context match before
 	and after each change.  When fewer lines of surrounding
-- 
1.6.0.2

-- 
Nanako Shiraishi
http://ivory.ap.teacup.com/nanako3/
Previous: Junio C Hamano
Message 6 of 6 in “What's cooking in git/spearce.git (Oct 2008, #02; Sun, 12)”
  1. Shawn O. PearceOct 12, 2008
  2. Junio C HamanoOct 13, 2008
  3. Junio C HamanoOct 13, 2008
  4. Stephen HabermanOct 13, 2008
  5. Junio C HamanoOct 13, 2008
  6. rebase: Document --no-verify option to bypass pre-rebase hookNanako Shiraishi, Oct 13, 2008

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.