RE: Subversion and Remote Repository Synchronization

2011-10-07 Thread Les Mikesell
On Oct 7, 2011 8:27 AM, "Bob Archer" wrote: > > > On Thu, Oct 6, 2011 at 12:55 PM, Daniel Shahaf > > wrote: > > Of course, the other solution is get a faster/bigger pipe to reduce the transfer times. > The issue may be more latency on operations that wait for handshakes than pure bandwidth. Usi

RE: Subversion and Remote Repository Synchronization

2011-10-07 Thread Bob Archer
> On Thu, Oct 6, 2011 at 12:55 PM, Daniel Shahaf > wrote: > > David Weintraub wrote on Thu, Oct 06, 2011 at 12:22:33 -0400: > >> 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

Re: Subversion and Remote Repository Synchronization

2011-10-06 Thread Mark Phippard
On Thu, Oct 6, 2011 at 4:23 PM, David Weintraub wrote: >> 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

Re: Subversion and Remote Repository Synchronization

2011-10-06 Thread David Weintraub
> 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

Re: Subversion and Remote Repository Synchronization

2011-10-06 Thread Les Mikesell
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

Re: Subversion and Remote Repository Synchronization

2011-10-06 Thread Daniel Shahaf
Les Mikesell wrote on Thu, Oct 06, 2011 at 13:25:58 -0500: > On Thu, Oct 6, 2011 at 12:55 PM, Daniel Shahaf > wrote: > > David Weintraub wrote on Thu, Oct 06, 2011 at 12:22:33 -0400: > >> What about using "svngit"? We could have an automated process that > >> pulls data from the Subversion reposi

Re: Subversion and Remote Repository Synchronization

2011-10-06 Thread Les Mikesell
On Thu, Oct 6, 2011 at 12:55 PM, Daniel Shahaf wrote: > David Weintraub wrote on Thu, Oct 06, 2011 at 12:22:33 -0400: >> 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

Re: Subversion and Remote Repository Synchronization

2011-10-06 Thread Daniel Shahaf
David Weintraub wrote on Thu, Oct 06, 2011 at 12:22:33 -0400: > 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 In

Re: Subversion and Remote Repository Synchronization

2011-10-06 Thread Mark Phippard
On Thu, Oct 6, 2011 at 12:22 PM, David Weintraub wrote: > Let's say I have a team in the U.S. where my Subversion repository is > kept, and I have a remote team in India. The remote team in India is > complaining about the length of time for checkouts and commits. Is > there a solution to this par

Re: Subversion and Remote Repository Synchronization

2011-10-06 Thread Ed
Subversion is not disributed - try svnsync for a while, most of the pain should go away otherwise check out http://www.wandisco.com/ On Thu, Oct 6, 2011 at 9:22 AM, David Weintraub wrote: > Let's say I have a team in the U.S. where my Subversion repository is > kept, and I have a remote team in I

Subversion and Remote Repository Synchronization

2011-10-06 Thread David Weintraub
Let's say I have a team in the U.S. where my Subversion repository is kept, and I have a remote team in India. The remote team in India is complaining about the length of time for checkouts and commits. Is there a solution to this particular issue in Subversion? I could create a local Svnsync repo