Skip to content

Commit

Permalink
fix documentation for git-commit --no-verify
Browse files Browse the repository at this point in the history
Despite what the documentation claims, git-commit does not check commit
for suspicious lines: all hooks are disabled by default,
and the pre-comit hook could be changed to do something else.

Signed-off-by: Michael S. Tsirkin <mst@mellanox.co.il>
Signed-off-by: Junio C Hamano <junkio@cox.net>
  • Loading branch information
Michael S. Tsirkin authored and Junio C Hamano committed Jan 12, 2007
1 parent 4494c65 commit fc41be3
Showing 1 changed file with 2 additions and 6 deletions.
8 changes: 2 additions & 6 deletions Documentation/git-commit.txt
Original file line number Diff line number Diff line change
Expand Up @@ -72,12 +72,8 @@ OPTIONS
Add Signed-off-by line at the end of the commit message.

--no-verify::
By default, the command looks for suspicious lines the
commit introduces, and aborts committing if there is one.
The definition of 'suspicious lines' is currently the
lines that has trailing whitespaces, and the lines whose
indentation has a SP character immediately followed by a
TAB character. This option turns off the check.
This option bypasses the pre-commit hook.
See also link:hooks.html[hooks].

-e|--edit::
The message taken from file with `-F`, command line with
Expand Down

0 comments on commit fc41be3

Please sign in to comment.