提交 fabbd8f6 编写于 作者: J J. Bruce Fields

user-manual: fix inconsistent use of pull and merge

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: N"J. Bruce Fields" <bfields@citi.umich.edu>
上级 923642fe
...@@ -1133,17 +1133,9 @@ modified in two different ways in the remote branch and the local ...@@ -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: branch--then you are warned; the output may look something like this:
------------------------------------------------- -------------------------------------------------
$ git pull . next $ git merge next
Trying really trivial in-index merge... 100% (4/4) done
fatal: Merge requires file-level merging Auto-merged file.txt
Nope.
Merging HEAD with 77976da35a11db4580b80ae27e8d65caf5208086
Merging:
15e2162 world
77976da goodbye
found 1 common ancestor(s):
d122ed4 initial
Auto-merging file.txt
CONFLICT (content): Merge conflict in file.txt CONFLICT (content): Merge conflict in file.txt
Automatic merge failed; fix conflicts and then commit the result. Automatic merge failed; fix conflicts and then commit the result.
------------------------------------------------- -------------------------------------------------
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册