Merge branch 'en/doc-merge-tree-describe-merge-base' into next
Clarify the "--merge-base" command line option in "git merge-tree". * en/doc-merge-tree-describe-merge-base: Documentation/git-merge-tree.adoc: clarify the --merge-base optionnext
commit
787ff6f08a
|
@ -79,11 +79,17 @@ OPTIONS
|
||||||
|
|
||||||
--merge-base=<tree-ish>::
|
--merge-base=<tree-ish>::
|
||||||
Instead of finding the merge-bases for <branch1> and <branch2>,
|
Instead of finding the merge-bases for <branch1> and <branch2>,
|
||||||
specify a merge-base for the merge, and specifying multiple bases is
|
specify a merge-base for the merge. This option is incompatible with
|
||||||
currently not supported. This option is incompatible with `--stdin`.
|
`--stdin`.
|
||||||
+
|
+
|
||||||
As the merge-base is provided directly, <branch1> and <branch2> do not need
|
Specifying multiple bases is currently not supported, which means that when
|
||||||
to specify commits; trees are enough.
|
merging two branches with more than one merge-base, using this option may
|
||||||
|
cause merge results to differ from what `git merge` would compute. This
|
||||||
|
can include potentially losing some changes made on one side of the history
|
||||||
|
in the resulting merge.
|
||||||
|
+
|
||||||
|
With this option, since the merge-base is provided directly, <branch1> and
|
||||||
|
<branch2> do not need to specify commits; trees are enough.
|
||||||
|
|
||||||
-X<option>::
|
-X<option>::
|
||||||
--strategy-option=<option>::
|
--strategy-option=<option>::
|
||||||
|
|
Loading…
Reference in New Issue