Re: What's your prefered revision control system?

I really like SVN, but I also like CVS but I really wish there was somehow the best of both worlds.

SVN's directory-based version control has so many benefits in the projects we use them, as we have many hidden files and its ability to track files that don't exist in one checkout of a repository yet when updating are fantastic.

The downfall is when you are the type who pragmatically commit and update single files rather than an entire repository. I don't trust my fingers, and I don't trust other peoples. When I commit a project, I commit the files that I know are ones I've touched to make sure that only those ones are what are going to be updated. Same goes for making updates on a repository.

SVN throws a big wrench in that, as when you make commits and updates in that fashion, and then want to update everything else in a checkout, it doesn't check the files that are there against the repository, it just says.. well you updated to this revision and I'm not going to second guess you.

It gets very annoying. But it's better than CVS at least.

Comment on Re: What's your prefered revision control system?

Replies are listed 'Best First'.
Re^2: What's your prefered revision control system? by jepri (Parson) on Sep 30, 2004 at 04:11 UTC
That does sound bad, but is it really necessary to check in individual files? This is what a RCS is all about for me - if I check in the wrong file, I can just go "whoops, revert". How do I know I checked a bad file in? My testing procedures will catch it, of course :) My SVN client offers me a list of files to approve before I check them in. It's graphical, but I'm happy to cope with that since I only run it once a day. Perhaps that shows what I'm doing wrong. ___________________ Jeremy I didn't believe in evil until I dated it.	[reply]
Re^2: What's your prefered revision control system? by eric256 (Parson) on Oct 05, 2004 at 01:00 UTC
SVN throws a big wrench in that, as when you make commits and updates in that fashion, and then want to update everything else in a checkout, it doesn't check the files that are there against the repository, it just says.. well you updated to this revision and I'm not going to second guess you. What? I may not realy understand what you are saying but I recently learned the joy of version control using SVN. I must say it works quite well. It allows you to commit single files (or directories). You can then also update your other files. If you updated a file it checks it agianst the repository to make sure that the version you started with is the same version currently commited. I can't seem to get my head around what you are trying to say it does. ___________ Eric Hodges	[reply]


more useful options
	PerlMonks