> 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 http://www.thornleyware.com [EMAIL PROTECTED] _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
