[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Importing from a working copy ... bad idea?

From: Eric Johnson <eric_at_tibco.com>
Date: Wed, 17 Apr 2019 16:32:08 -0700

Sounds like you might want to take advantage of svn:externals.

http://svnbook.red-bean.com/nightly/en/svn.advanced.externals.html

Eric.

On Wed, Apr 17, 2019 at 3:51 PM Mun Johl <mun.johl_at_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
>
Received on 2019-04-18 01:32:32 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.