After presenting multiple examples of trivial merges produced with the
merge command, we must apologize to our reader for what could be seen as confusing and contradictory: we pushed rather far the extent of the acknowledgement that we would describe a mechanism, not recommend a process.
Let's make our point explicit: any merges resulting in mere duplication of data are to be avoided whenever possible. Note how this precisely condemns trivial and copy merges!
SCM attempts to factor commonalities and make real differences stand out. On the contrary, using both of two identical versions introduces spurious differences into the dependency tree of dependent artifacts, and results in invalidating derived objects for artificial reasons. ...