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

> 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.

Shouldn't even have to do that most of the time. If you are looking
at the chain of revisions from some node-revision X to the beginning
of the node, and you see the same copy property on several of them in
a row, you know that the property applies only to the least recent
revision in the chain.

This also means we can just use a property named "copy" (or "svn:copy"
or "somelongurlprefixinventedbygregstein:copy") with the rev/path as
value, and that will provide enough information. The next time a copy
is performed along that line of development, it will overwrite the
property with a new value; in the meantime, the property just sticks
around and doesn't mean anything.
Received on Sat Oct 21 14:36:25 2006