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

Re: commiting to two repositories

From: Daniel Luis dos Santos <daniel.dlds_at_gmail.com>
Date: Wed, 1 Apr 2009 16:47:47 +0100

I want to continue using the repository I have locally. I just want to
send periodic versions to the remote repository that is available on
the internet.
 From time to time I would commit a new revision to the remote which
would be the latest version on the local

On Apr 1, 2009, at 4:04 PM, Paul Koning wrote:

>>>>>> "Daniel" == Daniel Luis dos Santos <daniel.dlds_at_gmail.com>
>>>>>> writes:
>
> Daniel> Hello, I have a subversion repository on a local machine that
> Daniel> I use for development. I also want to commit to another
> Daniel> repository on a remote machine. ...
>
> Daniel> Is there an easier way ?
>
> What is the purpose of this setup?
>
> If you have a remote repository as a backup or mirror, then the answer
> is simple: use svnsync (in the background, periodically or every
> commit, your choice) to keep the mirror up to date.
>
> If the secondary repository has *different* content from the primary,
> but parts of it are common, that won't work. It's hard to tell what
> the requirement is.
>
> One way to do "two repositories that have partly common stuff" is to
> have three repositories: the third has the common stuff. That third
> is hosted at one of the two sites but mirrored (svnsync) to the
> other. Each of the other two (non-common) repositories references the
> common repository (its local copy) via svn external links.
>
> paul
>

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1508227

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-04-01 17:48:59 CEST

This is an archived mail posted to the Subversion Users mailing list.