Adam Turoff writes: > 3) Those developers prefer Perforce and should not be forced > to use CVS because non-committers prefer it. > > Is there anything more to be said about Perforce vs. CVS that *isn't* FUD? You make it sound like we've decided on Perforce. Dan, how about you sketch out what you're thinking of (Perforce plus CVS, several committers, whatever it is) and give us a few use cases. How does some random person submit a patch? How does someone claim a unit to code? How do people stay current? Then we can hear informed criticism and perhaps modify the plan if a better system is suggested. Nat
- Re: code repository Bradley M. Kuhn
- Re: code repository Ask Bjoern Hansen
- Re: code repository Dan Sugalski
- Re: code repository Bradley M. Kuhn
- Re: code repository Bennett Todd
- Re: code repository Dan Sugalski
- Re: code repository Bennett Todd
- Re: code repository Dan Sugalski
- Re: code repository Alan Burlison
- Re: code repository Adam Turoff
- Re: code repository Nathan Torkington
- Re: code repository Michael G Schwern
- Re: code repository Nathan Torkington
- Re: code repository Bennett Todd
- Re: code repository Dan Sugalski
- Re: code repository Adam Turoff
- Can perforce gateway to CVS without los... Bradley M. Kuhn
- Re: Can perforce gateway to CVS without... Dan Sugalski
- Can perforce gateway to CVS without los... Nick Ing-Simmons
- Re: Can perforce gateway to CVS without... Barrie Slaymaker
- Re: Can perforce gateway to CVS without... Barrie Slaymaker