No subject

Independent of that, on a semantic level merges usually aren't
symmetric. Bookmarks point to different lines of development and if a
developer decides that line X should have changes from line Y
included, it does not imply that he wants Y to include all changes
from X.


> It should be broken because of the use case I explained in the part you
> deleted? But it seems that I'm not getting through, so I'll let the
> bookmark guys explain it instead...
>
> --
> Martin Geisler
>
> aragost Trifork
> Professional Mercurial support
> http://aragost.com/en/services/mercurial/blog/
>

--
Oben