blob: 58731c194229e7e14b4eca27465fd42894d9a710 [file] [log] [blame]
Junio C Hamano54559c82006-04-13 07:45:121git-merge-tree(1)
2=================
3
4NAME
5----
6git-merge-tree - Show three-way merge without touching index
7
8
9SYNOPSIS
10--------
Junio C Hamano15567bc2011-07-23 00:51:5911[verse]
Junio C Hamanofce7c7e2008-07-02 03:06:3812'git merge-tree' <base-tree> <branch1> <branch2>
Junio C Hamano54559c82006-04-13 07:45:1213
14DESCRIPTION
15-----------
Junio C Hamanoe6f28d02013-09-17 21:34:0016Reads three tree-ish, and output trivial merge results and
Junio C Hamano54559c82006-04-13 07:45:1217conflicting stages to the standard output. This is similar to
Junio C Hamanoec87f522008-12-10 08:35:2518what three-way 'git read-tree -m' does, but instead of storing the
Junio C Hamano54559c82006-04-13 07:45:1219results in the index, the command outputs the entries to the
20standard output.
21
22This is meant to be used by higher level scripts to compute
Junio C Hamanoec87f522008-12-10 08:35:2523merge results outside of the index, and stuff the results back into the
Junio C Hamano54559c82006-04-13 07:45:1224index. For this reason, the output from the command omits
Junio C Hamanoec87f522008-12-10 08:35:2525entries that match the <branch1> tree.
Junio C Hamano54559c82006-04-13 07:45:1226
Junio C Hamano54559c82006-04-13 07:45:1227GIT
28---
Junio C Hamanof7c042d2008-06-06 22:50:5329Part of the linkgit:git[1] suite