thanks! getting sure about this relieves me :)
anyway, the procedure you detail about doing
it on the wc may be cheap on the server, but
of course "expensive" on the local harddisk.
2007/4/11, Ryan Schmidt <subversion-2007b@ryandesign.com>:
> On Apr 11, 2007, at 11:35, marc gonzalez-carnicer wrote:
>
> > Some customers of ours created a svn repository
> > without the recommended directory structure of
> > trunk, branches and tags. That is, they have all
> > their folders in /, and that includes versioning
> > several binary files such as .jar, .exe, not all
> > of them small. And there are many revisions.
> >
> > Now they feel they may need to make some
> > branching. In principle, that is simple, it only
> > needs creating the trunk, branches and tags
> > folders, and then perform 3 svn mv of the 3
> > project main folders.
> >
> > However, I am hesitant that the mv (or the
> > intrinsic cp) may not be that "cheap" as
> > this term is defined in the svn book. Am I
> > being too paranoid? I would not like their server
> > to collapse.
>
> If you use "svn mv" it will be a cheap copy. You can check out a
> working copy of the entire repo, use "svn mkdir" to make the trunk,
> branches and tags directories, then "svn mv" all the other
> directories into the trunk, then commit in one revision. Or you can
> use "svn mkdir" and "svn mv" on the repository URLs and do it that
> way in several revisions. Or you can use mucc (the multiple-URL
> command client) to do it with URLs all in one revision. Doesn't
> matter; the copies will be "cheap" in any case.
>
> --
>
> To reply to the mailing list, please use your mailer's Reply To All
> function
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Apr 11 19:07:00 2007