Re: DESIGN: modelling working copy replacements

> > The current branch status> > ===================> >> > In an initial commit after branch creation, breser committed> > file-replacement. After that Ivan submitted patches to bring working> > copy administration up to date.> >> > After that, several tests have been committed and the same solution> > has been implemented for properties.> > So, to be clear, properties are no longer an "unaddressed" feature, but a> completed one?
Yes, that's right. > Are copy and move operations with this end result going to be re-enabled as> part of this branch, or is that regarded as a separate enhancement that depends> on this one?
Re-enabling copy and move is part of the branch effort and arequirement (in my mind) to qualify for merging the features intotrunk.
bye,

Erik.
Received on Fri Sep 9 14:16:08 2005