[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: Mun Johl <mun.johl_at_kazan-networks.com>
Date: Thu, 18 Apr 2019 16:10:31 +0000

Hi Lorenz,

Thank you for your reply.
Please see my comments below.

On Wed, Apr 17, 2019 at 10:28 PM PDT, Lorenz wrote:
>
> 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.

Agreed; that does seem to be the consensus.

> Your concern regarding complecety: is this about the clutter the many
> separate copies will create in the log?

Not so much the clutter in the log, per se. But just the execution of
all the requisite 'svn copy' invocations that will be needed to
construct the new_project directory structure. It's almost like hand
picking a few hundred files scattered throughout a repository and
copying them into one new directory structure in SVN.

> 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.

Hmm, I was not aware of svnmucc. But after reading about svnmucc I
think what I would need to do is create the directory structure I want
outside of a valid workspace; and then write a script that would use
'svnmucc mkdir' and 'svnmucc put' to populate the ^/trunk/new_project
directory.

Does that sound pretty close? If I am understanding things correctly, I
like that solution very much.

Thank you and regards,

-- 
Mun
Received on 2019-04-18 18:34:15 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.