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

Yoshiki Hayashi <yoshiki@xemacs.org> writes:
> Since these are done by one trail (one DB transaction), the
> order of above three operation doesn't matter. So you can
> first create a new fs revision and then walk through mutable
> nodes. When the function finds a mutable node, it checks
> whether it is a copy node or not and if it is, it replaces
> base fs revision field of copy property.

Yes, that would certainly work. It's kind of ugly, though, for the
filesystem to be wonking on node properties. It would be really nice
if we could come up with an entirely client-side approach.
Received on Sat Oct 21 14:36:25 2006