summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLibravatar Stephan Beyer <s-beyer@gmx.net>2008-06-08 03:36:08 +0200
committerLibravatar Junio C Hamano <gitster@pobox.com>2008-06-08 13:46:38 -0700
commitbc47c29ec18164ba1f05600333457cf6f2432856 (patch)
treedab182d9aabbba3f09abf8e83ddd9e5a7e8df1a9
parentgit-send-email: allow whitespace in addressee list (diff)
downloadtgif-bc47c29ec18164ba1f05600333457cf6f2432856.tar.xz
git-commit.txt: Add missing long/short options
Also split the "-c or -C <commit>" item into two separate items. Signed-off-by: Stephan Beyer <s-beyer@gmx.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
-rw-r--r--Documentation/git-commit.txt17
1 files changed, 9 insertions, 8 deletions
diff --git a/Documentation/git-commit.txt b/Documentation/git-commit.txt
index 40bf63ea63..af52728943 100644
--- a/Documentation/git-commit.txt
+++ b/Documentation/git-commit.txt
@@ -57,14 +57,16 @@ OPTIONS
been modified and deleted, but new files you have not
told git about are not affected.
--c or -C <commit>::
- Take existing commit object, and reuse the log message
+-C <commit>|--reuse-message=<commit>::
+ Take an existing commit object, and reuse the log message
and the authorship information (including the timestamp)
- when creating the commit. With '-C', the editor is not
- invoked; with '-c' the user can further edit the commit
- message.
+ when creating the commit.
--F <file>::
+-c <commit>|--reedit-message=<commit>::
+ Like '-C', but with '-c' the editor is invoked, so that
+ the user can further edit the commit message.
+
+-F <file>|--file=<file>::
Take the commit message from the given file. Use '-' to
read the message from the standard input.
@@ -85,7 +87,7 @@ OPTIONS
-s|--signoff::
Add Signed-off-by line at the end of the commit message.
---no-verify::
+-n|--no-verify::
This option bypasses the pre-commit and commit-msg hooks.
See also linkgit:githooks[5][hooks].
@@ -112,7 +114,6 @@ OPTIONS
further edit the message taken from these sources.
--amend::
-
Used to amend the tip of the current branch. Prepare the tree
object you would want to replace the latest commit as usual
(this includes the usual -i/-o and explicit paths), and the