Code

user-manual: fix inconsistent use of pull and merge
authorJ. Bruce Fields <bfields@citi.umich.edu>
Sun, 11 Mar 2007 02:52:39 +0000 (21:52 -0500)
committerJ. Bruce Fields <bfields@citi.umich.edu>
Sun, 11 Mar 2007 04:05:01 +0000 (23:05 -0500)
I used "git pull ." instead of "git merge" here without any explanation.
Stick instead to "git merge" for now (the equivalent pull syntax is
still covered in a later chapter).

Cc: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
Signed-off-by: "J. Bruce Fields" <bfields@citi.umich.edu>
Documentation/user-manual.txt

index 8b5709ba75f328ad1e99c998ea50bc99791725c4..f4ea967191686f749796d94de28db59db10d0ade 100644 (file)
@@ -1133,17 +1133,9 @@ modified in two different ways in the remote branch and the local
 branch--then you are warned; the output may look something like this:
 
 -------------------------------------------------
-$ git pull . next
-Trying really trivial in-index merge...
-fatal: Merge requires file-level merging
-Nope.
-Merging HEAD with 77976da35a11db4580b80ae27e8d65caf5208086
-Merging:
-15e2162 world
-77976da goodbye
-found 1 common ancestor(s):
-d122ed4 initial
-Auto-merging file.txt
+$ git merge next
+ 100% (4/4) done
+Auto-merged file.txt
 CONFLICT (content): Merge conflict in file.txt
 Automatic merge failed; fix conflicts and then commit the result.
 -------------------------------------------------