Mun Johl wrote:
>We're using SVN version 1.8.19 on Red Hat Enterprise Linux 6.8 .
>
>For a new project we are about to undertake, I need to create a new
>directory in our repository (let's call it ^/trunk/new_project).
>However, most of the directories/files in the "new_project" directory
>will come from other areas of the same repository that are being
>consolidated into a new directory.
>
>I was thinking of creating this new directory structure and then doing
>an 'svn import'. However, that will result in the loss of the existing
>logs, right?
>
>If I want to maintain the logs of the leveraged files, is my only
>recourse to use 'svn copy' to get all of the leveraged files into
>"new_project"? Unfortunately, that will add a lot of complexity for the
>100's of files that will need to reside under ^/trunk/new_project.
svn copy sounds like the way to go.
Your concern regarding complecety: is this about the clutter the many
separate copies will create in the log?
In this case you can either checkout all relevant paths and do the
copying int the working copy, or you could use svnmucc (subversions
'multi URL command client') and script the whole process into one
commit.
--
Lorenz
Received on 2019-04-18 07:29:30 CEST