Re: Cloning, branching, and cvs2svn

I'm afraid I don't really understand Ben's response to your questions;
he seemed to think you were asking about the filesystem database
rather than the user-visible semantics. I'm going to try responding
based on my own understanding, and people can correct me if I'm wrong.

> 1. Is it possible to clone a file as well as a directory?

Certainly, since a clone is just a copy.

> 2. Can a clone go anywhere in the tree?

Again, of course it can; you can copy a file or directory from
anywhere in the tree to anywhere else, as one would expect.

> 3. Has a UI for this been decided yet? Does it need anything more
> than "svn clone originalURL newURL"?

For creating something analagous to a CVS branch, I'm not sure why
we'd need any UI other than "svn cp". For creating something
analagous to a CVS tag, we might want something simpler than "svn cp"
followed by an ACL change, but that's what it would boil down to.

> 5. Finally, is it all right if some of the later examples go on to
> use the links that you were proposing, that I suggested calling
> "references"?

I don't know what our plans are here, but I can explain to Ben what
you mean. By a "reference", you mean something like a Unix hard link,
such that if you did:

  svn ln foo bar; svi ci
  svn rm foo/blah; svn ci

bar/blah would also disappear. Likewise, if you edited a file under
foo, the changes would appear under bar, and vice versa.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:44 2006