subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Weintraub <>
Subject Re: Subversion and Remote Repository Synchronization
Date Thu, 06 Oct 2011 20:23:44 GMT
> On Thu, Oct 6, 2011 at 1:51 PM, Daniel Shahaf <> wrote:
>>> >> What about using "svngit"? We could have an automated process that
>>> >> pulls data from the Subversion repository in the U.S. and creates a
>>> >> local Git repository in India using "svngit'. This could be done when
>>> >> there's no one in the Indian office. Developers could then checkout
>>> >> and commit their changes to their local Git repository. In the middle
>>> >> of the night, the Git repository could then push its changes to
>>> >> Subversion using "gitsvn" Is this a possibility?

On Thu, Oct 6, 2011 at 3:49 PM, Les Mikesell <> wrote:
> I don't have experience with using git-svn myself, but it seems to be
> designed to handle that scenario.

Svn-git was mainly designed to allow you to checkpoint your work
without checking in code you know might not work.

What I am thinking is something a bit more radical: Using Git as a
local repository for a remote Subversion repository. Now, you're
talking about 10 to 20 or more users in your remote site using Git,
pushing their changes to the local central Git repository, and then
having that central Git repository sync itself back to the Subversion
repository. You're hope is that the site that has the Subversion
repository isn't doing to many changes while the remote site is
active. And, the remote site isn't active while the local site is
committing changes into Subversion.

I like the Perforce proxy. It's practically invisible to the user and
really speeds things up.

I was thinking that I could script a MultiSite solution with
Subversion without too much difficulty. I started working on the
project and realized that there was a major problem. With ClearCase
MultiSite, your repositories will match version for version. In my
Subversion imitation, I was getting the sync done correctly, and the
trees and changes matched. However, the revision numbering was off
between the two sites.

Since most people use the Subversion revision numbering as an
alternative to tags, the mismatch in revision numbers would be
unacceptable. And, the "svn logs" don't match, so it becomes difficult
to match the history.

David Weintraub

View raw message