> Date: Tue, 05 Nov 2002 16:42:20 +0100 > From: Robert Epprecht <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Re: cvs: two repositories > > On Monday 04 November 2002 11:15 pm, Robert Epprecht wrote: > I'm developping a program which I would like to put somewhere on > the net like savannah or sourceforge. As I am on a slow modem > connection I would prefer to keep my local cvs repository and sync > the public one from time to time, bundling some related commits > in one upload. How can I do that?
Bob: This probably isn't what you want to hear, and I'm not familiar w/ subversion, but - It's incredibly difficult to keep physically separate source code repositories in sync. My advice is to pick one, probably the remote host (you mentioned SourceForge or savannah) and designate it as the master. Then, create a local repository and treat it as the slave. This has the distinct advantage of unilaterally declaring that all tags are relevant only in the master repository. It also has the advantage that you can use the slave repository for intermediate (WIP) check-ins and update the master when appropriate. w/r/t the slow modem, remember that CVS supports compression via the "-z" qualifier. If you're new to CVS, check out TkCVS, It's a nice CVS GUI; its CVSROOT/modules extension is quite useful. Maybe subversion has a magic bullet for this problem; I'm sure others on the list will post an appropriate comment. I've not used CVS in dual mode as you asked. I have tried to support another, very similar, source code control system (DEC/Compaq/HP CMS) in that mode, and it was a failure; especially when multiple developers got involved, or some module got updated locally, but never made it to the remote library. I don't know how hirsute you are, but when designing a source code control strategy, proceed with the intention of keeping all your hair. HTH, jec -- Microsoft Free By 2003 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
