I blog about debugging, development using .net, C#, SQL, and other Microsoft technologies.
Disclaimer: All posts are provided "AS IS" with no warranties, confering no rights, and expressing only my personal opinion, not Microsoft's.
A previous post was dedicated to show the benefits of a baseless merge, this one shows the pitfalls:
The 3-way merge shows you the changes in source with respect to the base version, and the changes in target with respect to the base version. However, in a baseless merge, by definition, there’s no such thing. Hence, you will see the changes in each file with respect to the other.
Generally speaking, you should avoid baseless merge as you can. If you need to port changes between branches that share a common parent, reverse-integrate (RI) from the source branch to that common parent then forward-integrate (FI) to the target branch.
PingBack from http://www.codedstyle.com/pitfalls-of-baseless-merge-8/
PingBack from http://www.codedstyle.com/pitfalls-of-baseless-merge/