Re: M-x big-picture

> O.K., that's all clear as long as the source is a file. If it's a
> directory, we actually want to copy the whole tree. So it seems to
> me that we have to create copies of its children when they change,
> but I've seen discussions about creating branches instead.

I think we will wind up creating branches instead.

The purpose of a copy node is to preserve the information about a
copy. (Not that we have a way for clients to get at that information
yet.) It remains the case that two different files (foo/xxx and
bar/xxx, if foo was copied to bar) might live in the same node. The
information about what happened should still be there if you look hard
enough.
Received on Sat Oct 21 14:36:20 2006