tutorial: misc updates.
Signed-off-by: Junio C Hamano <junkio@cox.net>
Junio C Hamano committed
Jan 3, 2007 at 08:38 UTC
c1d179f88add2a8c1e0052d34cf757760c25b8df
1 file changed
+17
-7
Documentation/tutorial.txt
+17
-7
@@ -65,16 +65,19 @@ Try modifying some files, then run
65
$ git diff
66
------------------------------------------------
67
68
-to review your changes. When you're done,
68
+to review your changes. When you're done, tell git that you
69
+want the updated contents of these files in the commit and then
70
+make a commit, like this:
71
72
------------------------------------------------
71
-$ git commit file1 file2...
73
+$ git add file1 file...
74
+$ git commit
75
------------------------------------------------
76
74
-will again prompt your for a message describing the change, and then
77
+This will again prompt your for a message describing the change, and then
78
record the new versions of the files you listed. It is cumbersome
76
-to list all files and you can say `-a` (which stands for 'all')
77
-instead.
79
+to list all files and you can say `git commit -a` (which stands for 'all')
80
+instead of running `git add` beforehand.
81
82
------------------------------------------------
83
$ git commit -a
@@ -84,7 +87,7 @@ A note on commit messages: Though not required, it's a good idea to
87
begin the commit message with a single short (less than 50 character)
88
line summarizing the change, followed by a blank line and then a more
89
thorough description. Tools that turn commits into email, for
87
-example, use the first line on the Subject line and the rest of the
90
+example, use the first line on the Subject: line and the rest of the
91
commit in the body.
92
93
@@ -142,6 +145,13 @@ If you also want to see complete diffs at each step, use
145
$ git log -p
146
------------------------------------------------
147
148
+Often the overview of the change is useful to get a feel of
149
+each step
150
+
151
+------------------------------------------------
152
+$ git log --stat --summary
153
+------------------------------------------------
154
+
155
Managing branches
156
-----------------
157
@@ -381,7 +391,7 @@ commit.
391
$ git show c82a22c39cbc32576f64f5c6b3f24b99ea8149c7
392
-------------------------------------
393
384
-But there other ways to refer to commits. You can use any initial
394
+But there are other ways to refer to commits. You can use any initial
395
part of the name that is long enough to uniquely identify the commit:
396
397
-------------------------------------