Merge branch 'jc/ll-merge-binary-ours'
"git merge -Xtheirs" did not help content-level merge of binary files; it should just take their version. Also "*.jpg binary" in the attributes did not imply they should use the binary ll-merge driver. * jc/ll-merge-binary-ours: ll-merge: warn about inability to merge binary files only when we can't attr: "binary" attribute should choose built-in "binary" merge driver merge: teach -Xours/-Xtheirs to binary ll-merge driver
This commit is contained in:
@ -927,7 +927,7 @@ file at the toplevel (i.e. not in any subdirectory). The built-in
|
||||
macro attribute "binary" is equivalent to:
|
||||
|
||||
------------
|
||||
[attr]binary -diff -text
|
||||
[attr]binary -diff -merge -text
|
||||
------------
|
||||
|
||||
|
||||
|
@ -32,13 +32,14 @@ ours;;
|
||||
This option forces conflicting hunks to be auto-resolved cleanly by
|
||||
favoring 'our' version. Changes from the other tree that do not
|
||||
conflict with our side are reflected to the merge result.
|
||||
For a binary file, the entire contents are taken from our side.
|
||||
+
|
||||
This should not be confused with the 'ours' merge strategy, which does not
|
||||
even look at what the other tree contains at all. It discards everything
|
||||
the other tree did, declaring 'our' history contains all that happened in it.
|
||||
|
||||
theirs;;
|
||||
This is opposite of 'ours'.
|
||||
This is the opposite of 'ours'.
|
||||
|
||||
patience;;
|
||||
With this option, 'merge-recursive' spends a little extra time
|
||||
|
Reference in New Issue
Block a user