Skip to content

Commit 92043e9

Browse files
committed
Merge branch 'en/doc-merge-tree-describe-merge-base' into maint-2.51
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 option
2 parents d204057 + 1c573a3 commit 92043e9

File tree

1 file changed

+10
-4
lines changed

1 file changed

+10
-4
lines changed

Documentation/git-merge-tree.adoc

Lines changed: 10 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -78,11 +78,17 @@ OPTIONS
7878
7979
--merge-base=<tree-ish>::
8080
Instead of finding the merge-bases for <branch1> and <branch2>,
81-
specify a merge-base for the merge, and specifying multiple bases is
82-
currently not supported. This option is incompatible with `--stdin`.
81+
specify a merge-base for the merge. This option is incompatible with
82+
`--stdin`.
8383
+
84-
As the merge-base is provided directly, <branch1> and <branch2> do not need
85-
to specify commits; trees are enough.
84+
Specifying multiple bases is currently not supported, which means that when
85+
merging two branches with more than one merge-base, using this option may
86+
cause merge results to differ from what `git merge` would compute. This
87+
can include potentially losing some changes made on one side of the history
88+
in the resulting merge.
89+
+
90+
With this option, since the merge-base is provided directly, <branch1> and
91+
<branch2> do not need to specify commits; trees are enough.
8692
8793
-X<option>::
8894
--strategy-option=<option>::

0 commit comments

Comments
 (0)