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

RE: How to synchronize two subversion servers?

From: <Chris.Fouts_at_qimonda.com>
Date: 2006-12-11 17:18:10 CET

Won't it just be easier to create your branch off the project
repos and do your work there? Your branch is essentially
your "private" repository. Of course if you're not allowed
to create a branch that's an issue.


        From: Pablo F [mailto:caladris@googlemail.com]
        Sent: Thursday, December 07, 2006 2:41 PM
        To: users@subversion.tigris.org
        Subject: How to synchronize two subversion servers?
        Hi all,
        I have a conceptual problem about subversion. The issue is that
I want to download the source code of a project and import it into my
personal subversion server to develop by myself the code. But I want to
update the modifications of the project in my personal subversion server
as well. I explain with more details in the following lines:
        1. Checkout from, say tigris.org to tmp1 (to simplify the case I
suppose the project has only a file)
        /tmp1$: svn checkout
http://svn.tigris.org/repos/svn/trunk/project1 (version 234)
        2. List the files I downloaded:
        ls /tmp/tmp1
        3. I delete all .svn directories of tmp1.
        4. I import the result to my server:
        /tmp$:svn import -m "New import" tmp1
        5. I work with my personal repository committing changes.
        6. Sometime I'm in the version 20 of file1 and I want to update
the changes of the project repository, which it's now at version 250, in
my personal repository to make the version 21 of file1. I don't know how
to manage this. There is a special solution of how to synchronise these
two servers?
        Thanks a lot and sorry for this little mess!
        Pablo F.
Received on Mon Dec 11 17:33:26 2006

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.