diff options
author | Junio C Hamano <gitster@pobox.com> | 2022-12-14 18:47:54 +0900 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2022-12-14 18:47:54 +0900 |
commit | 505bc6a44061b7c9c044c29c5784d49897fe101c (patch) | |
tree | 87f3a7d986f130b7f9c54590253d95abbed3810c /git-merge-tree.txt | |
parent | 823b19959deb06ddbdfbeab7128f10558178fb42 (diff) | |
download | git-htmldocs-505bc6a44061b7c9c044c29c5784d49897fe101c.tar.gz |
Autogenerated HTML docs for v2.39.0-56-g57e2c
Diffstat (limited to 'git-merge-tree.txt')
-rw-r--r-- | git-merge-tree.txt | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/git-merge-tree.txt b/git-merge-tree.txt index 04bcc416e..88ee94210 100644 --- a/git-merge-tree.txt +++ b/git-merge-tree.txt @@ -64,6 +64,11 @@ OPTIONS share no common history. This flag can be given to override that check and make the merge proceed anyway. +--merge-base=<commit>:: + Instead of finding the merge-bases for <branch1> and <branch2>, + specify a merge-base for the merge, and specifying multiple bases is + currently not supported. This option is incompatible with `--stdin`. + [[OUTPUT]] OUTPUT ------ @@ -216,6 +221,17 @@ with linkgit:git-merge[1]: * any messages that would have been printed to stdout (the <<IM,Informational messages>>) +INPUT FORMAT +------------ +'git merge-tree --stdin' input format is fully text based. Each line +has this format: + + [<base-commit> -- ]<branch1> <branch2> + +If one line is separated by `--`, the string before the separator is +used for specifying a merge-base for the merge and the string after +the separator describes the branches to be merged. + MISTAKES TO AVOID ----------------- |