Tutorial: fix asciidoc formatting of "git add" section.
Signed-off-by: Junio C Hamano <junkio@cox.net>
Junio C Hamano committed
Feb 2, 2007 at 22:19 UTC
953202a3fd68f84210cfe9bf102c534ac3ee40e4
1 file changed
+18
-18
Documentation/tutorial.txt
+18
-18
@@ -101,27 +101,27 @@ want to commit together. This can be done in a few different ways:
101
102
1) By using 'git add <file_spec>...'
103
104
- This can be performed multiple times before a commit. Note that this
105
- is not only for adding new files. Even modified files must be
106
- added to the set of changes about to be committed. The "git status"
107
- command gives you a summary of what is included so far for the
108
- next commit. When done you should use the 'git commit' command to
109
- make it real.
110
-
111
- Note: don't forget to 'add' a file again if you modified it after the
112
- first 'add' and before 'commit'. Otherwise only the previous added
113
- state of that file will be committed. This is because git tracks
114
- content, so what you're really 'add'ing to the commit is the *content*
115
- of the file in the state it is in when you 'add' it.
104
+This can be performed multiple times before a commit. Note that this
105
+is not only for adding new files. Even modified files must be
106
+added to the set of changes about to be committed. The "git status"
107
+command gives you a summary of what is included so far for the
108
+next commit. When done you should use the 'git commit' command to
109
+make it real.
110
+
111
+Note: don't forget to 'add' a file again if you modified it after the
112
+first 'add' and before 'commit'. Otherwise only the previous added
113
+state of that file will be committed. This is because git tracks
114
+content, so what you're really 'add'ing to the commit is the *content*
115
+of the file in the state it is in when you 'add' it.
116
117
2) By using 'git commit -a' directly
118
119
- This is a quick way to automatically 'add' the content from all files
120
- that were modified since the previous commit, and perform the actual
121
- commit without having to separately 'add' them beforehand. This will
122
- not add content from new files i.e. files that were never added before.
123
- Those files still have to be added explicitly before performing a
124
- commit.
119
+This is a quick way to automatically 'add' the content from all files
120
+that were modified since the previous commit, and perform the actual
121
+commit without having to separately 'add' them beforehand. This will
122
+not add content from new files i.e. files that were never added before.
123
+Those files still have to be added explicitly before performing a
124
+commit.
125
126
But here's a twist. If you do 'git commit <file1> <file2> ...' then only
127
the changes belonging to those explicitly specified files will be