"Eric Smith" <eric-svn@brouhaha.com> writes:
> > So, our recommendation would have been for you to instead
> > import like so:
> >
> > svn import tsbutils svn+ssh://svn.example.com/tsbutils/trunk
>
> Another message explained that (though without the example command).
> I deleted and recreated my repository and did that, and it works great.
>
> If I *didn't* put my stuff one level down, and then I wanted to create
> a branch by copying, would it cause a problem? In other words, if
> I did this:
> svn copy svn+ssh://svn.example.com/ svn+ssh://svn.example.com/branch/foo
>
> Even if that doesn't cause a problem, then if I later want to create a
> second branch:
> svn copy svn+ssh://svn.example.com/ svn+ssh://svn.example.com/branch/bar
>
> Won't that second branch also include a branch of the first branch
> (branch/foo)?
Yep, you seem to have a firm grasp on the "branch by copy" concept.
> If so, it seems like it would be a *very* good idea for the book and
> man page to stronly discourage imports (and checkins) at the top
> level.
Hm... yeah, that does seem like a strong point to make. Besides --
the last thing you want is to come back from a week at the beach, run
'svn update' on your "trunk" working copy and, because all the
branches are subdirs of that directory, get full checkouts of all the
branches that your co-workers made while you were on vacation. :-)
> Also, it would be nice if the book would explain the "-t" option to
> svnserve.
Noted.
> I'd be willing to work on the proposed doc changes if you like, though
> since I'm a Subversion novice I'd want someone to check my work before
> committing it.
Sure, go for it.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Aug 4 20:59:15 2003