Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to email@example.com.
Andreas Krey wrote: > This is not what the patch does, obviously. It chooses the diff from > 1.2 to 220.127.116.11 to be merged into the head. You need to used the base > of the last merge arrow as the base version for the merge, not the tip. But 1.2 is *not* an ancestor of 18.104.22.168, so the merge is bogus. All you've done is degraded merge into a simple copy. In a true merging situation the two branches can easily follow independent paths and never be identical to each other - mergepoints are designed to help you extract the difference between two points on the *same* branch. What you seem to want is not mergepoints but a copy operation. Tony