Autogenerated manpages for v1.5.3-rc4-16-ga76c

diff --git a/man1/git-commit.1 b/man1/git-commit.1
index da381a1b1d15af73e7477b7b0ae106983f18c0e8..a3c48344f06bca7c164a2ef3cbd1d396d224a94b 100644 (file)
--- a/man1/git-commit.1
+++ b/man1/git-commit.1
@@ -2,7 +2,7 @@
 .\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
 .\" Instead of manually editing it, you probably should edit the DocBook XML
 .\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT\-COMMIT" "1" "07/27/2007" "Git 1.5.3.rc3.13.g7ab3" "Git Manual"
+.TH "GIT\-COMMIT" "1" "08/06/2007" "Git 1.5.3.rc4.16.ga76c" "Git Manual"
 .\" disable hyphenation
 .nh
 .\" disable justification (adjust text to left margin only)
@@ -18,21 +18,20 @@ git\-commit \- Record changes to the repository
            [\-\-] [[\-i | \-o ]<file>\&...]
 .fi
 .SH "DESCRIPTION"
-Use \fIgit commit\fR when you want to record your changes into the repository along with a log message describing what the commit is about. All changes to be committed must be explicitly identified using one of the following methods:
+Use \fIgit commit\fR to store the current contents of the index in a new commit along with a log message describing the changes you have made.
+
+The content to be added can be specified in several ways: 1. by using \fBgit\-add\fR(1) to incrementally "add" changes to the index before using the \fIcommit\fR command (Note: even modified files must be "added");
 .TP 3
 1.
-by using \fBgit\-add\fR(1) to incrementally "add" changes to the next commit before using the \fIcommit\fR command (Note: even modified files must be "added");
+by using \fBgit\-rm\fR(1) to remove files from the working tree and the index, again before using the \fIcommit\fR command;
 .TP
 2.
-by using \fBgit\-rm\fR(1) to identify content removal for the next commit, again before using the \fIcommit\fR command;
+by listing files as arguments to the \fIcommit\fR command, in which case the commit will ignore changes staged in the index, and instead record the current content of the listed files;
 .TP
 3.
-by directly listing files containing changes to be committed as arguments to the \fIcommit\fR command, in which cases only those files alone will be considered for the commit;
+by using the \-a switch with the \fIcommit\fR command to automatically "add" changes from all known files (i.e. all files that are already listed in the index) and to automatically "rm" files in the index that have been removed from the working tree, and then perform the actual commit;
 .TP
 4.
-by using the \-a switch with the \fIcommit\fR command to automatically "add" changes from all known files i.e. files that have already been committed before, and to automatically "rm" files that have been removed from the working tree, and perform the actual commit.
-.TP
-5.
 by using the \-\-interactive switch with the \fIcommit\fR command to decide one by one which files should be part of the commit, before finalizing the operation. Currently, this is done by invoking git\-add \-\-interactive.
 
 The \fBgit\-status\fR(1) command can be used to obtain a summary of what is included by any of the above for the next commit by giving the same set of parameters you would give to this command.