A user unfamiliar with CVS might not realize that a git-add is
needed before commiting new files. So emphasize that "git commit
<path>..." only commits files already in the index.
Signed-off-by: Jonathan Nieder <jrnieder@xxxxxxxxxxxx>
---
I keep on forgetting and getting annoyed when "git commit
newfile.c" does not work. From the same confusion I suggested
git commit -A without really thinking about what it meant.
This change should make the behavior easier to understand
and remember. Thanks for the help.
Documentation/git-commit.txt | 7 ++++---
1 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/Documentation/git-commit.txt b/Documentation/git-commit.txt
index 0e25bb8..9b00ccb 100644
--- a/Documentation/git-commit.txt
+++ b/Documentation/git-commit.txt
@@ -27,9 +27,10 @@ The content to be added can be specified in several ways:
2. by using 'git-rm' to remove files from the working tree
and the index, again before using the 'commit' command;
-3. by listing files as arguments to the 'commit' command, in which
- case the commit will ignore changes staged in the index, and instead
- record the current content of the listed files;
+3. by listing some known files as arguments to the 'commit'
+ command, in which case the commit will ignore changes staged
+ in the index and instead record the current content of the
+ listed files;
4. by using the -a switch with the 'commit' command to automatically
"add" changes from all known files (i.e. all files that are already
--
1.6.0.rc1.91.gf0c3
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
