649
I Use This!
Activity Not Available

Ratings and Reviews

Analyzed over 1 year ago. based on code collected over 1 year ago.
Community Rating
2.8956
   

Average Rating:   2.9/5.0
Number of Ratings:   182
Number of Reviews:   4

My Review of CVS: Concurrent Versions System

You have not rated or reviewed this project.
Click below to rate/review.
My Rating:
0
 
 New Review

Most Helpful Reviews

rds says:
Really getting old  
3.0
   
written about 15 years ago

CVS is good thanks to its popularity and frequent integration in most tools (IDE, software factories, well just about everywhere).

However, it's old, does not handle change sets and does not version directories. The only SCM I know which has less features I know is PVCS.

If you use CVS, it is really time to move to subversioN.

5 out of 7 users found the following review helpful.

Did this review help you? |

Hendrik ... says:
CVS vs. Subversion  
5.0
 
written over 13 years ago

CVS is very stable. In case of an hardware failure it does not destroy the repository like Subversion does. The worst case is some stale lock files lying around, which are automatically deleted on reboot by most Linux distributions.

CVS does support unique IDs for commits spanning multiple directories.

Popular CVS clients like Eclipse do support change sets.

CVS has very handy short version numbers on a per file basis. "You need version one point twenty four of database.php" is so much nicer "than you need version sixmillionthreehundretninetyeightthousandfivehundretandfourtytwo.

CVS does supports adding commit logs and version identifiers to files.

CVS is commonly supported by IDEs without installing unofficial plugins.

1 out of 2 users found the following review helpful.

Did this review help you? |

asdsad says:
Any updates?  
5.0
 
written almost 10 years ago

?!

Did this review help you? |

Most Recent Reviews

asdsad says:
Any updates?  
5.0
 
written almost 10 years ago

?!

Did this review help you? |

myfreeweb says:
What? CVS?  
2.0
   
written almost 13 years ago

It's really old thing. Go Bazaar!

0 out of 1 users found the following review helpful.

Did this review help you? |

Hendrik ... says:
CVS vs. Subversion  
5.0
 
written over 13 years ago

CVS is very stable. In case of an hardware failure it does not destroy the repository like Subversion does. The worst case is some stale lock files lying around, which are automatically deleted on reboot by most Linux distributions.

CVS does support unique IDs for commits spanning multiple directories.

Popular CVS clients like Eclipse do support change sets.

CVS has very handy short version numbers on a per file basis. "You need version one point twenty four of database.php" is so much nicer "than you need version sixmillionthreehundretninetyeightthousandfivehundretandfourtytwo.

CVS does supports adding commit logs and version identifiers to files.

CVS is commonly supported by IDEs without installing unofficial plugins.

1 out of 2 users found the following review helpful.

Did this review help you? |

rds says:
Really getting old  
3.0
   
written about 15 years ago

CVS is good thanks to its popularity and frequent integration in most tools (IDE, software factories, well just about everywhere).

However, it's old, does not handle change sets and does not version directories. The only SCM I know which has less features I know is PVCS.

If you use CVS, it is really time to move to subversioN.

5 out of 7 users found the following review helpful.

Did this review help you? |

 See all reviews