summaryrefslogtreecommitdiff
path: root/Documentation/tutorial.txt
diff options
context:
space:
mode:
authorJunio C Hamano <junkio@cox.net>2007-02-03 06:19:17 (GMT)
committerJunio C Hamano <junkio@cox.net>2007-02-03 06:19:17 (GMT)
commit953202a3fd68f84210cfe9bf102c534ac3ee40e4 (patch)
treee63df67c3c507ac4d42c461b308025232789cb1a /Documentation/tutorial.txt
parent3cf8b462d2dbe78233bba5c0765ecaa2c6b6cd99 (diff)
downloadgit-953202a3fd68f84210cfe9bf102c534ac3ee40e4.zip
git-953202a3fd68f84210cfe9bf102c534ac3ee40e4.tar.gz
git-953202a3fd68f84210cfe9bf102c534ac3ee40e4.tar.bz2
Tutorial: fix asciidoc formatting of "git add" section.
Signed-off-by: Junio C Hamano <junkio@cox.net>
Diffstat (limited to 'Documentation/tutorial.txt')
-rw-r--r--Documentation/tutorial.txt36
1 files changed, 18 insertions, 18 deletions
diff --git a/Documentation/tutorial.txt b/Documentation/tutorial.txt
index adb1e32..ea34189 100644
--- a/Documentation/tutorial.txt
+++ b/Documentation/tutorial.txt
@@ -101,27 +101,27 @@ want to commit together. This can be done in a few different ways:
1) By using 'git add <file_spec>...'
- This can be performed multiple times before a commit. Note that this
- is not only for adding new files. Even modified files must be
- added to the set of changes about to be committed. The "git status"
- command gives you a summary of what is included so far for the
- next commit. When done you should use the 'git commit' command to
- make it real.
-
- Note: don't forget to 'add' a file again if you modified it after the
- first 'add' and before 'commit'. Otherwise only the previous added
- state of that file will be committed. This is because git tracks
- content, so what you're really 'add'ing to the commit is the *content*
- of the file in the state it is in when you 'add' it.
+This can be performed multiple times before a commit. Note that this
+is not only for adding new files. Even modified files must be
+added to the set of changes about to be committed. The "git status"
+command gives you a summary of what is included so far for the
+next commit. When done you should use the 'git commit' command to
+make it real.
+
+Note: don't forget to 'add' a file again if you modified it after the
+first 'add' and before 'commit'. Otherwise only the previous added
+state of that file will be committed. This is because git tracks
+content, so what you're really 'add'ing to the commit is the *content*
+of the file in the state it is in when you 'add' it.
2) By using 'git commit -a' directly
- This is a quick way to automatically 'add' the content from all files
- that were modified since the previous commit, and perform the actual
- commit without having to separately 'add' them beforehand. This will
- not add content from new files i.e. files that were never added before.
- Those files still have to be added explicitly before performing a
- commit.
+This is a quick way to automatically 'add' the content from all files
+that were modified since the previous commit, and perform the actual
+commit without having to separately 'add' them beforehand. This will
+not add content from new files i.e. files that were never added before.
+Those files still have to be added explicitly before performing a
+commit.
But here's a twist. If you do 'git commit <file1> <file2> ...' then only
the changes belonging to those explicitly specified files will be