--- Nathan <[EMAIL PROTECTED]> wrote: > I second the suggestion to go with Subversion, and not CVS. > We used CVS at my work until we tried Subversion a few years > ago-we switched and never looked back. Subversion is waaaay > better.
Both have their good and bad points. I prefer CVS for most projects, although to Subversion's credit, it does offer atomic commits and better support for Unicode files. Why do I prefer CVS, then? - Independent revision numbers per file, rather than a single number for the entire project - Better branching and tagging - I've seen too many cases where Subversion's Berkeley DB repositories have been corrupted or left in a locked state, preventing everyone from updating or committing until an administrator can fix things. In partial response to this problem, Subversion has added the ability to make a repository using the native filesystem instead of BDB, but BDB is still the default. - Subversion keeps a second copy of every file in the project in hidden subdirectories within the working copy. Besides being a ridiculous waste of disk space (keep in mind, I use a laptop, so disk is at something of a premium), this also causes problems when doing multi-file operations like "find . -type f ..." or "foreach i (`grep -rl foo .`) ..." . The rationale for this design was that disk is cheap and you're not always connected to the network. I disagree. On a laptop, disk is expensive, and between WiFi and EVDO, you pretty much *are* always connected to the network if you want to be. -------------------- BYU Unix Users Group http://uug.byu.edu/ The opinions expressed in this message are the responsibility of their author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG. ___________________________________________________________________ List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
