Comment 7 for bug 875698

But in my example, there are two merges -- the one that adds c, and the other that adds b. When uncommiting and reverting, b gets deleted, c gets unversioned. What makes bzr behave differently in these two cases?

I could contribute by testing various corner cases, but I don't know enough about bzrlib internals to be able to properly fix this issue.