Hi Eric, Thank you for your reply. Please see my comments below.
On Wed, Apr 17, 2019 at 04:32 PM PDT, Eric Johnson wrote: > Sounds like you might want to take advantage of svn:externals. > > http://svnbook.red-bean.com/nightly/en/svn.advanced.externals.html I was not familiar with svn:externals, so thank you for the link. However, if I understand the concept correctly--which is a big IF--I don't think that's the solution I want to use. It seems that svn:externals allows users to easily checkout piece-meal files from a repo and create a new structure. Perhaps analogous to symbolic links (yeah, that might be a stretch). However, I don't want updates to affect the original files since they are still pertinent to other projects. What I want is to create a _new_ SVN directory by leveraging those files and hopefully maintaining their svn log information during their initial commit to the new project. Thanks and Regards, -- Mun > Eric. > > On Wed, Apr 17, 2019 at 3:51 PM Mun Johl > <mun.j...@kazan-networks.com<mailto:mun.j...@kazan-networks.com>> wrote: > Hi, > > 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. > > Any suggestions would be welcomed. > > Regards, > > -- > Mun
