Hi Nathan, Please see my comments below.
On Wed, Apr 17, 2019 at 07:01 PM PDT, Nathan Hartman wrote: > On Wed, Apr 17, 2019 at 8:01 PM Mun Johl > <mun.j...@kazan-networks.com<mailto:mun.j...@kazan-networks.com>> wrote: > 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. > > In that case it sounds more like you'd want to do a copy, same as you would > for branching but into the new project directory. As long as the source and > destination projects exist in the same repository, Subversion will be able to > trace the history of those files back through to the source project. That's what I thought. I was just hoping for an easier solution since the source directories are spread out within the repository. And often the entire directory does not need to be copied; rather, just specific files. I appreciate your feedback, Nathan. Kind regards, -- Mun
