Re: Re: cvs: php4 /pear/Experimental README/pear/Experimental/HTML Menu.php

From: Date: Sat, 10 Mar 2001 05:19:23 +0000
Subject: Re: Re: cvs: php4 /pear/Experimental README/pear/Experimental/HTML Menu.php
References: 1 2 3 4 5  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-8@lists.php.net to get a copy of this message
On Sat, Mar 10, 2001 at 01:23:22AM +0100, Stig Sther Bakken wrote: > > Branches are an excellent approach when used properly. The > > post-experimenal-cycle merges might be difficult for those who aren't > > already experienced with cvs, however. > > Yes, that's my main problem with it, too. But you don't really avoid > this kind of problem (fixing conflicts during a merge) with other > solutions either? Good point. =) > > As a side note, maybe Perforce would be a better choice than cvs for > > this sort of repository? Just a suggestion. I like them both. =) > > What is Perforce? (IMHO, any CVS replacement has to offer > _significant_ benefits if I am ever to consider a move of anything. > CVS is just too well-integrated with people's software and minds. :-) It's a very powerful (commercial but free for open source projects) source management system. More information at http://www.perforce.com/. I only mentioned it because of its superior branching and merging capabilities. We're probably best off sticking with cvs because so many people understand it already. -- Jon Parise (jon@csh.rit.edu) . Rochester Inst. of Technology http://www.csh.rit.edu/~jon/ : Computer Science House Member

« previous php.pear.dev (#8) next »