On Tue, Mar 12, 2013 at 8:44 PM, Branko Čibej <[email protected]> wrote: ... > I have to agree with Mark. As long as we don't know how to track a > mixed-revision move in all cases, then it's better to revert to copy+delete > than to block the move. Ideally only for those parts of the move source that > are actually out of date with regard to the repository, but I take it we > haven't got that far yet.
Random thought: can move tracking be "repaired" after the fact? If there were an API to do so, users / GUI's could repair such "broken (legacy) moves" at some point (either automatically or at the request of the user after he's gotten some hint by the GUI (and perhaps after some operations such as updating, if necessary)). -- Johan
