No generally accepted algorithm exists for merging the contents of binary-format files. But it is quite possible for a binary-format element to get into an
overlap state in a concurrent development environment.
Example: Two team members might each revise the corporate logo file using an image editor, and then
Keep it. One of them then
Promotes the file to the backing stream, creating an overlap situation in the other workspace.
To resolve a binary-file overlap, you invoke the Merge command, just as for a text file. The Binary Merge dialog appears.
This invokes the Revert to Backed command, which resolves the situation by purging the
(overlap)-status version from your workspace. The workspace reverts to using the version of the file that was in the backing stream at the previous update.