这里准备碎片化地去解读和理解 Git 的一些功能。关于 git-merge 的总结一直没有做，但是几乎每天都会遇到 git-merge，而且会遇到很多随着 merge 而产生的问题，所以只好碎片化地去做一做整理。
git-merge 有两种 merge 方式，ff 方式和 true merge 方式，关于 ff 的方式，另外一篇文章有讲过，这里不再赘述，这里整理一下 true merge，真实 merge。
Except in a fast-forward merge (see above), the branches to be merged must be tied together by a merge commit that has both of them as its parents.
真实 merge 是真的去 merge 一下，而不是像 ff 那样，只是把一个 commit 放过来，从这个角度来说，ff 不是有点像 cherry-pick 吗？
A merged version reconciling the changes from all branches to be merged is committed, and your HEAD, index, and working tree are updated to it. It is possible to have modifications in the working tree as long as they do not overlap; the update will preserve them.
一个 merge 的版本融合了（reconcile 的意思是调节，放在这里有点不好理解，所以解释为融合）所有要被 merge 的分支的改变，并且会被提交，这样你的 HEAD、index、working tree 都会被更新。
When it is not obvious how to reconcile the changes, the following happens:
The HEAD pointer stays the same.
The MERGE_HEAD ref is set to point to the other branch head.
Paths that merged cleanly are updated both in the index file and in your working tree.
For conflicting paths, the index file records up to three versions: stage 1 stores the version from the common ancestor, stage 2 from HEAD, and stage 3 from MERGE_HEAD (you can inspect the stages with git ls-files -u). The working tree files contain the result of the “merge” program; i.e. 3-way merge results with familiar conflict markers <<< === >>>.
3路 merge，公共祖先、HEAD、MERGE_HEAD（是指另外那个分支的 HEAD） 这三个方面来 merge。
If you tried a merge which resulted in complex conflicts and want to start over, you can recover with git merge –abort.
git merge --abort 回滚吧。
关于HEAD、index、worktree、local repository、remote repository的关系，请参考这里，这个挺重要，随后要整理一下。
The merge mechanism (git merge and git pull commands) allows the backend merge strategies to be chosen with -s option. Some strategies can also take their own options, which can be passed by giving -X
git merge 和 git pull 命令使用的 merge 机制允许通过 -s 选项后面的 merge 策略被选择。
This can only resolve two heads (i.e. the current branch and another branch you pulled from) using a 3-way merge algorithm. It tries to carefully detect criss-cross merge ambiguities and is considered generally safe and fast.
This can only resolve two heads using a 3-way merge algorithm. When there is more than one common ancestor that can be used for 3-way merge, it creates a merged tree of the common ancestors and uses that as the reference tree for the 3-way merge. This has been reported to result in fewer merge conflicts without causing mismerges by tests done on actual merge commits taken from Linux 2.6 kernel development history. Additionally this can detect and handle merges involving renames, but currently cannot make use of detected copies. This is the default merge strategy when pulling or merging one branch.
The recursive strategy can take the following options:
This option forces conflicting hunks to be auto-resolved cleanly by favoring our version. Changes from the other tree that do not conflict with our side are reflected to the merge result. For a binary file, the entire contents are taken from our side.
This should not be confused with the ours merge strategy, which does not even look at what the other tree contains at all. It discards everything the other tree did, declaring our history contains all that happened in it.
This is the opposite of ours; note that, unlike ours, there is no theirs merge strategy to confuse this merge option with.
-X<option>参数，可以指定合并策略，上面摘录了两种，一种是 resolve，一种是recursive，第一种策略看上去似乎是可以自动解决冲突，第二种是 Git 默认的 merge 策略，会产生一些少量的冲突，而不会进行错误的合并，它还有几个选项，就是合并时，只选择本地的（ours），或者只选择别人的（theirs）。