Return-Path: X-Original-To: apmail-subversion-users-archive@minotaur.apache.org Delivered-To: apmail-subversion-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DB7834D8B for ; Mon, 6 Jun 2011 11:23:27 +0000 (UTC) Received: (qmail 3980 invoked by uid 500); 6 Jun 2011 11:23:27 -0000 Delivered-To: apmail-subversion-users-archive@subversion.apache.org Received: (qmail 3954 invoked by uid 500); 6 Jun 2011 11:23:27 -0000 Mailing-List: contact users-help@subversion.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@subversion.apache.org Received: (qmail 3947 invoked by uid 99); 6 Jun 2011 11:23:27 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Jun 2011 11:23:27 +0000 X-ASF-Spam-Status: No, hits=0.0 required=5.0 tests=FREEMAIL_FROM,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [217.140.74.2] (HELO continuum.iocl.org) (217.140.74.2) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Jun 2011 11:23:21 +0000 Received: (from krey@localhost) by continuum.iocl.org (8.11.3/8.9.3) id p56BMv210645; Mon, 6 Jun 2011 13:22:57 +0200 Date: Mon, 6 Jun 2011 13:22:57 +0200 From: Andreas Krey To: "Randolph, Christian [USA]" Cc: "users@subversion.apache.org" Subject: Re: Two-Site Subversion Repository Setup Ideas Message-ID: <20110606112257.GD5178@inner.h.iocl.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-message-flag: What did you expect to see here? On Sun, 05 Jun 2011 14:57:22 +0000, Randolph, Christian [USA] wrote: ... > Is there a way to setup the two subversion repositories to somehow automate keeping the two repositories in sync? No (AFAIF, as usual), not out of the box. > We are usually passing media back and forth once a week, but currently we are doing a manual sync process that is both time-consuming and error-prone. I don't think that there is a way of synchronizing all branches of two svn repositories when different commit are made to each of them. It would be relatively easy to keep a single branch (say, trunk) synchronized with its brother on the other side, by carrying the tree back and forth, and doing some script magic. You need to remember the last revision you transported, though. (You will also lose renames, and svn:externals will be interesting.) The 'vendor model' won't work because it does not work with cyclic imports; it does not give the merge infos that are needed in this case. > Any suggestions would be greatly appreciated. The 'dirtiest' model of synchronization is to use git&svn in the same sandbox, with proper .ignores, and use the git repos for transfer. But that by itself is also somewhat error-prone. I use that on svn projects when I need to work on multiple machines, but it's not an industrial method. Andreas -- "Totally trivial. Famous last words." From: Linus Torvalds Date: Fri, 22 Jan 2010 07:29:21 -0800