Re: Copy node vs copy property (was Re: CVS update ...)

> In short, you also add fs revision number to property which
> indicates when it is copied.

It occurs to me that a node-revision can only be a copy of its
immediate predecessor. Storing the path/rev of the revision copied
from provides enough information to determine the copy history of a
node, even if you leave the properties around indefinitely.

(In other words, 100.3 can be a copy of some rev/path which refers to
100.2, but successors of 100.3 cannot be a copy of the same rev/path,
since a copy of the same rev/path would become 100.2.1.1 or some other
successor of 100.2.)
Received on Sat Oct 21 14:36:25 2006