[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Keeping multiple CVS repositories in sync

From: Chris Palmer
Subject: Re: Keeping multiple CVS repositories in sync
Date: Wed, 10 Jul 2002 10:40:35 -0700 (PDT)

Not to rub it in or anything...  it also seems that a pre-requisite
to providing access to remote developers to a CVS repository would
be having some kind of network connection.  Without that, what's the
point?  How are you going to get the data across between multiple
sites if you dont't even have basic connectivity?

I assume the real problem is that you've got a large amount of data  
and would rather not send the same data across between the 2 sites
for each developer doing checkouts.

Would the remote developers have access to Solaris hardware for the
mirrored repository?  or are they still limited to using only Win32?


Jay Yarbrough wrote
> Thank you for your response.
> It would appear for anyone who truly needs multiple repositories kept in sync,
> that CVS is an unacceptable tool.  This is most unfortunate.
> Our remote developers often cannot even get access to the internet.
> In spite of the optimism of another response, their limited access is real.
> As for using something other than Win32 as an OS, unfortunately, I cannot 
> dictate they learn an entirely new OS, and new tools to work on that OS.  
> Therefore, they will continue to work in a Win32 environment.
> Our need is to have them use an SCM tool that can support multiple 
> synchronized
> repositories.  Our preference would be to find a way to do this with CVS. 
> -----Original Message-----
> From: address@hidden [mailto:address@hidden
> Sent: Saturday, July 06, 2002 10:57 AM
> To: Jay Yarbrough
> Cc: address@hidden
> Subject: Re: Keeping multiple CVS repositories in sync
> > We have only recently begun to use CVS as our primary repository.  It is 
> hosted on a solaris-8 platform.  We are also sub-contracting some of our 
> software to remote developers who will only have access to Win32 systems.  
> Due to the flakey internet connections between their site and ours, it is 
> not practical to have them access our repository directly.
> >
> Please wrap your lines at fewer than 80 characters.
> Greg has addressed some of the other issues, so I'll ask how flakey
> the connections are, and why they can't use the repository directly.
> CVS has its greatest functionality when there's a high-speed link
> to the server, but it degrades very gracefully with worse connections,
> and it is often quite usable with relatively poor connections.
> If you were to supply your remote developers with a checked-out
> copy to begin with, that they could copy, you'd avoid the most
> bandwidth-intensive part of using CVS.  After that, they'd need to
> download updates (often in patch form) and upload changes (which
> would need to include the whole file(s)).
> -- 
> Now building a CVS reference site at
> address@hidden
> _______________________________________________
> Info-cvs mailing list
> address@hidden
> _______________________________________________
> Info-cvs mailing list
> address@hidden

reply via email to

[Prev in Thread] Current Thread [Next in Thread]