(Thanks,  since I've already said enough publicly, I'm replying just privately).

>> It seems that I'm the only one who thinks MC branches are not worth
>> their costs.  Our tools have bugs and limitations w.r.t. branch
>> support (like the selection-issue you mentioned in the meeting).  That
>> means we can either put our energy into fixing them, or put energy
>> into transitioning to something simpler (or, of course, do nothing,
>> which means we live with the bugs).  I, of course, prefer to simplify,
>> but since we are already this deep into them, I guess we'll just have
>> to manage it..
>
> Chris, there is no way around having _some_ kind of branching mechanism
> that supports multiple branches within the same repository. There is no

Why is "within same repository" a requirement?

> “simpler” there.
>   Without that we would fall years (decades?) behind other VCS, even
> SVN or CVS, and _I_ am not willing to swallow that. Sorry, but I know
> no way around this.

Many projects using MC but not using MC branches, you're saying their
SCM is decades behind?

Probably not, because you know MC uses its ancestry for that..