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

Chained svns

From: John Doe <jdmls_at_yahoo.com>
Date: Tue, 23 Sep 2008 05:15:40 -0700 (PDT)


I am new to the list, to svn and rcs in general...
I looked at the FAQ and the list's archives but did not find exactly what I was looking for.
Basicaly, we have an office, where we have devel and pre-production, and a production website hosted at a datacenter.
What would be the best way to setup this with subversion...?
One mandatory point: no rsync and no live svn update through the (potentialy unstable) network.

I was thinking of something like chained svns one at the office and one at the datacenter.
But I am a bit confused between branches, vendor branches and tags.
an office svn with a trunk (pre-prod) branch and a devel branch + a
datacenter svn with a vendor branch pointing to the office svn work...?
would go like merge devel into trunk at the office. Then merge "vendor
branch" (office trunk) at the datacenter. Then svn update localy at
the datacenter.
Does it make sence and/or is there an easier/better way to do this?



To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-09-23 14:16:13 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.