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.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||