CVS uses a client-server architecture: a server stores the current version(s) of a project and its history, and clients connect to the server in order to “check out” a complete copy of the project, work on this copy and then later “check in” their changes. Typically, the client and server connect over a LAN or over the Internet, but client and server may both run on the same machine if CVS has the task of keeping track of the version history of a project with only local developers.
1 Response to CVS – Open Source Version Control
Best Open Source Version Control Systems | Open Source Applications
November 27th, 2009 at 3:20 am
[...] 1. CVS – Open Source Version Control [...]