[Dev] Source Code Revision Control Infrastructure

[Nimret Sandhu]

> Yes, Perforce is god (actually just back from visiting their company 
> one hour ago), it 

i hope u meant good +)

> handling is also better, no need to worry about the -kb flags like with 
> CVS. 

u can setup the cvs repository to automatically add files with a certain xtension as binary so the clients dont have to.

> The really strong point with Perforce is doing multiple trees and 
> integrating code back to a baseline, this is why many companies have 
> gone with Perforce.

yep .. i have used perforce in the past also and really liked it. but cvs is ubiquitous.
 
> it's really 
> good, but you need to get used to the model of 
> checking-out-and-editing, rather than edit-tainted-check-in that CVS 
> has. --Kent

blech .. pls tell me that is not the default behaviour and i most certainly dont hope that it locks files ( ala vss). u have no hope to scale the # of devs on the project if u have lock/edit instead of a merge based system imo. i cant remmember how we had that setup ( i dont remmember locking files - but it was a few years ago).

does perforce handle security? cvs can be tunnelled over ssh. ssh also supports on the fly compression.

regs ~
nimret