Tutorial-2: Adjust git-status output to recent reality.
Signed-off-by: Junio C Hamano <junkio@cox.net>
Junio C Hamano committed
Feb 2, 2007 at 22:55 UTC
bf3478de973607ebe5b7689fa76e05c3f344aabd
1 file changed
+7
-8
Documentation/tutorial-2.txt
+7
-8
@@ -352,24 +352,23 @@ situation:
352
353
------------------------------------------------
354
$ git status
355
-#
356
-# Added but not yet committed:
357
-# (will commit)
355
+# On branch master
356
+# Changes to be committed:
357
+# (use "git reset HEAD <file>..." to unstage)
358
#
359
# new file: closing.txt
360
#
361
-#
362
-# Changed but not added:
363
-# (use "git add file1 file2" to include for commit)
361
+# Changed but not updated:
362
+# (use "git add <file>..." to update what will be committed)
363
#
364
# modified: file.txt
365
#
366
------------------------------------------------
367
368
Since the current state of closing.txt is cached in the index file,
370
-it is listed as "added but not yet committed". Since file.txt has
369
+it is listed as "Changes to be committed". Since file.txt has
370
changes in the working directory that aren't reflected in the index,
372
-it is marked "changed but not added". At this point, running "git
371
+it is marked "changed but not updated". At this point, running "git
372
commit" would create a commit that added closing.txt (with its new
373
contents), but that didn't modify file.txt.
374