Makes some cleanup/review in gittutorial
There are some different but little cleanup changes to fix some missing quotes, to fix what seemed to be an unended sentence, to reident a little paragraph with too large a sentence and fix a branch name that was referred to twice later by another name. Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Thadeu Lima de Souza Cascardo committed
Jun 29, 2009 at 12:13 UTC
21d777f2577a8003d12bdc1c5f3c1ff68750c598
1 file changed
+12
-12
Documentation/gittutorial.txt
+12
-12
@@ -332,11 +332,11 @@ alice$ git log -p HEAD..FETCH_HEAD
332
------------------------------------------------
333
334
This operation is safe even if Alice has uncommitted local changes.
335
-The range notation HEAD..FETCH_HEAD" means "show everything that is reachable
336
-from the FETCH_HEAD but exclude anything that is reachable from HEAD.
335
+The range notation "HEAD..FETCH_HEAD" means "show everything that is reachable
336
+from the FETCH_HEAD but exclude anything that is reachable from HEAD".
337
Alice already knows everything that leads to her current state (HEAD),
338
-and reviewing what Bob has in his state (FETCH_HEAD) that she has not
339
-seen with this command
338
+and reviews what Bob has in his state (FETCH_HEAD) that she has not
339
+seen with this command.
340
341
If Alice wants to visualize what Bob did since their histories forked
342
she can issue the following command:
@@ -375,9 +375,9 @@ it easier:
375
alice$ git remote add bob /home/bob/myrepo
376
------------------------------------------------
377
378
-With this, Alice can perform the first part of the "pull" operation alone using the
379
-'git-fetch' command without merging them with her own branch,
380
-using:
378
+With this, Alice can perform the first part of the "pull" operation
379
+alone using the 'git-fetch' command without merging them with her own
380
+branch, using:
381
382
-------------------------------------
383
alice$ git fetch bob
@@ -566,22 +566,22 @@ $ git log v2.5.. Makefile # commits since v2.5 which modify
566
567
You can also give 'git-log' a "range" of commits where the first is not
568
necessarily an ancestor of the second; for example, if the tips of
569
-the branches "stable-release" and "master" diverged from a common
569
+the branches "stable" and "master" diverged from a common
570
commit some time ago, then
571
572
-------------------------------------
573
-$ git log stable..experimental
573
+$ git log stable..master
574
-------------------------------------
575
576
-will list commits made in the experimental branch but not in the
576
+will list commits made in the master branch but not in the
577
stable branch, while
578
579
-------------------------------------
580
-$ git log experimental..stable
580
+$ git log master..stable
581
-------------------------------------
582
583
will show the list of commits made on the stable branch but not
584
-the experimental branch.
584
+the master branch.
585
586
The 'git-log' command has a weakness: it must present commits in a
587
list. When the history has lines of development that diverged and