blob: 58731c194229e7e14b4eca27465fd42894d9a710 [file] [log] [blame]
Junio C Hamanoc16e30c2006-04-13 00:09:54 -07001git-merge-tree(1)
2=================
3
4NAME
5----
6git-merge-tree - Show three-way merge without touching index
7
8
9SYNOPSIS
10--------
Martin von Zweigbergk7791a1d2011-07-01 22:38:26 -040011[verse]
Jonathan Niederb1889c32008-06-30 01:09:04 -050012'git merge-tree' <base-tree> <branch1> <branch2>
Junio C Hamanoc16e30c2006-04-13 00:09:54 -070013
14DESCRIPTION
15-----------
Richard Hansenbb8040f2013-09-04 15:04:30 -040016Reads three tree-ish, and output trivial merge results and
Junio C Hamanoc16e30c2006-04-13 00:09:54 -070017conflicting stages to the standard output. This is similar to
Ralf Wildenhues29b802a2008-12-09 07:23:51 +010018what three-way 'git read-tree -m' does, but instead of storing the
Junio C Hamanoc16e30c2006-04-13 00:09:54 -070019results 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
Ralf Wildenhues29b802a2008-12-09 07:23:51 +010023merge results outside of the index, and stuff the results back into the
Junio C Hamanoc16e30c2006-04-13 00:09:54 -070024index. For this reason, the output from the command omits
Ralf Wildenhues29b802a2008-12-09 07:23:51 +010025entries that match the <branch1> tree.
Junio C Hamanoc16e30c2006-04-13 00:09:54 -070026
Junio C Hamanoc16e30c2006-04-13 00:09:54 -070027GIT
28---
Christian Couder9e1f0a82008-06-06 09:07:32 +020029Part of the linkgit:git[1] suite