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

Re: Best way to copy project from one server to another, and then back

From: Ryan Schmidt <subversion-2010d_at_ryandesign.com>
Date: Fri, 22 Oct 2010 00:29:28 -0500

On Oct 21, 2010, at 23:37, mfass wrote:

> I have two subversion servers. One is an open source repository not
> controlled by me, and the other is a closed source repository which is
> controlled by me. Both the open source and the closed source build together
> to make one set of software. The closed source is a firewalled server at my
> place of employment. Currently we are in need to rename the project for a
> launch announcement at an upcoming conference.
>
> Becasue of the sensitive nature of the announcement, we cannot make the
> changes to the open source (sourceforge) project because our hosting service
> will not temporarily restrict anonymous access to the source code to just
> commiter's.
>
> To workaround this, we decided that we will pull the source code from the
> sourceforge project, into our internal, closed source repository. We then
> want to make the changes, and once the announcement of the naming etc. has
> been done, we can merge back to our sourceforge project the naming changes
> that were made.
>
> I was thinking of doing it via svn copy from one project to the other, and
> then taking the diff and copying back as we need.

You cannot "svn copy" between repositories, only within a repository.

Subversion really isn't designed to do what you propose. I don't have a better suggestion for you. Maybe someone else does.
Received on 2010-10-22 07:30:10 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.