Cloning, branching, and cvs2svn

A while ago I offered to help write use cases to help people understand how
to use clones, how to convert their existing branches into
directory-and-clone structures, and things like that. Right now my job
involves thinking hard about this sort of thing, so it is probably a
convenient time to start. First, though, I need to make sure I understand
it all properly. So:

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

2. Can a clone go anywhere in the tree? I'm guessing it can, as long as it
doesn't make a cycle, e.g. given

  a/b
  x/y

you could clone x as a/b/c to give

  a/b/c/y
  x/y

Is that right?

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

4. How much has been done with cvs2svn? It is going to need rules about
what to do with branches and tags, and it would probably be helpful if tags
with different names could be treated differently. Some, like those used to
help with merging, might not need to be preserved at all. I'm imagining a
file full of things like:

  product1 trunk products/product1
  product1 .* branches/product1/{branch}

  .* release([0-9]+) releases/{path}/{1}
  .* alpha alpha/{path}
  .* beta beta/{path}
  .* .* development/{path}/{branch}

I had a look at the cvs2svn sources, but didn't see much about branches or
tags.

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"?

Looking forward to learning more on Monday,

Peter.

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