Philip Martin <philip.mar...@wandisco.com> writes: > I don't understand this. You seem to be asking for move tracking to be > unreliable in order to avoid a message that tells users how to make move > work. When the user moves things around some of the 'moves' will show > up as moves and others will not. How is that sensible? How is the user > supposed to understand what is happening?
Further, one of the ways users get mixed-revision working copies is by committing. If one then moves such a mixed revision and it degrades to copy+delete it is not generally possible to commit the 'move' because some part of the delete will be out-of-date. If we don't make users update before move they often have to run update before comitting. If the users have to run update anyway it's far better to get them to do it before the move so that move tracking works. -- Philip