Autogenerated man pages for v1.2.0-g6a9b

[git.git] / man1 / git-commit.1

diff --git a/man1/git-commit.1 b/man1/git-commit.1
index 8400762..8dc0490 100755 (executable)
--- a/man1/git-commit.1
+++ b/man1/git-commit.1
@@ -23,8 +23,8 @@ git-commit \- Record your changes
 .SH "SYNOPSIS"
 
 .nf
-\fIgit\-commit\fR [\-a] [\-i] [\-s] [\-v] [(\-c | \-C) <commit> | \-F <file> | \-m <msg>]
-           [\-e] [\-\-author <author>] [\-\-] <file>...
+\fIgit\-commit\fR [\-a] [\-s] [\-v] [(\-c | \-C) <commit> | \-F <file> | \-m <msg>]
+           [\-e] [\-\-author <author>] [\-\-] [[\-i | \-o ]<file>...]
 .fi
 
 .SH "DESCRIPTION"
@@ -78,12 +78,16 @@ The message taken from file with \-F, command line with \-m, and from file with
 Instead of committing only the files specified on the command line, update them in the index file and then commit the whole index\&. This is the traditional behaviour\&.
 
 .TP
+\-o|\-\-only
+Commit only the files specified on the command line\&. This format cannot be used during a merge, nor when the index and the latest commit does not match on the specified paths to avoid confusion\&.
+
+.TP
 --
 Do not interpret any more arguments as options\&.
 
 .TP
 <file>...
-Commit only the files specified on the command line\&. This format cannot be used during a merge, nor when the index and the latest commit does not match on the specified paths to avoid confusion\&.
+Files to be committed\&. The meaning of these is different between \-\-include and \-\-only\&. Without either, it defaults \-\-only semantics\&.
 
 
 If you make a commit and then found a mistake immediately after that, you can recover from it with \fBgit\-reset\fR(1)\&.