Greg Hudson <ghudson@MIT.EDU> writes:
> > 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 18.104.22.168 or some other
> successor of 100.2.)
Ah hah! As I said, I was waiting for someone to be clever.
So, when we find some node revision C with a copy property (REV,
PATH), then we look up PATH in REV to find the original, some node
revision O. If C is not an immediate successor of O, then the copy
property doesn't apply to C.
Received on Sat Oct 21 14:36:25 2006