> > Wrong. Subversion's file:// access method goes straight to it. The worst of > this is the tendency of Windows people to put the repository on a shared file > server with multiple users using the file:// method on the same repository at > the same time.
Not wrong at all. CVS and RCS have the same thing, you can make your "server" be some directory somewhere else on your local disk. Which I pointed out actually. It doesn't mater where the "server" is. CVS, SVN and Perforce are all client-server designs. Period. Which, if you'll notice, you acknowledge the weakness of getting around the client-server design of SVN by directly accessing via the file:// access method on shared Windows discs (CVS has a similar bad history with people trying to put it on NFS mounts BTW). Look, I'm not really interested in a religious debate of "my VCS is better than your VCS". You like SVN. Good for you. Enjoy. I simply thought the original poster would like a pointer to an excellent VCS that certainty makes sense for a single developer (heck, I use it to version my Linux /etc config files, and I never expect anyone else to look at those) to use in a local workspace, no external server, be it a real server or a different directory, required. Git -> powerful, simple, and local. Jack, Do some research, try some out, kick a few tires and find the one that works best with your workflow. Each has pluses and minuses, but until you try one for a while you won't know what works for you. My recommendation (other than try Git), is stay away from CVS, there's no need for that pain. Also, I wouldn't bother with any commercial systems, the Open Source ones are all generally as good or better, and for a single developer the commercial systems wouldn't make much sense anyway. A good start: https://secure.wikimedia.org/wikipedia/en/wiki/List_of_revision_control_software - Steve -- You received this message because you are subscribed to the "BBEdit Talk" discussion group on Google Groups. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at <http://groups.google.com/group/bbedit?hl=en> If you have a feature request or would like to report a problem, please email "[email protected]" rather than posting to the group. Follow @bbedit on Twitter: <http://www.twitter.com/bbedit>
