merge-recursive: match the unmerged index entry behaviour with merge-resolve
[git/jnareb-git.git] / Documentation / git-resolve.txt
blob4e57c2b2877b1594b3a467c0930348221e98c672
1 git-resolve(1)
2 ==============
4 NAME
5 ----
6 git-resolve - Merge two commits
9 SYNOPSIS
10 --------
11 'git-resolve' <current> <merged> <message>
13 DESCRIPTION
14 -----------
15 Given two commits and a merge message, merge the <merged> commit
16 into <current> commit, with the commit log message <message>.
18 When <current> is a descendant of <merged>, or <current> is an
19 ancestor of <merged>, no new commit is created and the <message>
20 is ignored.  The former is informally called "already up to
21 date", and the latter is often called "fast forward".
24 Author
25 ------
26 Written by Linus Torvalds <torvalds@osdl.org> and
27 Dan Holmsand <holmsand@gmail.com>.
29 Documentation
30 --------------
31 Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel.org>.
33 GIT
34 ---
35 Part of the gitlink:git[7] suite