Run a merge for files needing merging
gitmerge -index [ -o] [ -q] <merge -program> ( -a | [ --] <file>*)
-- Do not interpret any more arguments as options .
-a Run merge against all files in the index that need merging .
-o Instead of stopping at the first failed merge, do all of them in one shot -continue with merging even when previous merges returned errors, and only return the error code after all the merges .
-q Do not complain about a failed merge program (a merge program failure usually indicates conflicts during the merge) . This is for porcelains which might want to emit custom messages .
torvalds@ppc970:~/merge -test> git merge -index cat MM This is MM from the original tree . # original This is modified MM in the branch A . # merge1 This is modified MM in the branch B . # merge2 This is modified MM in the branch B . # current contents .RE or .RS 4
torvalds@ppc970:~/merge -test> git merge -index cat AA MM cat: : No such file or directory This is added AA in the branch A . This is added AA in the branch B . This is added AA in the branch B . fatal: merge program failed .RE where the latter example shows how gitmerge -index will stop trying to merge once anything has returned an error (i .e ., cat returned an error for the AA file, because it didn exist in the original, and thus gitmerge -index didn even try to merge the MM thing) .