On Jul 13, 2011, at 12:08 AM, Steve deRosier wrote: >> 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.
You said to the effect one must "set up a server no matter its only you and your laptop." Suspect you are confused with the popularity of using WEBDAV with svn. This is all it takes (without WEBDAV): mkdir testproject cd testproject/ svnadmin create /Users/dkelly/SVNROOT touch testfile.c svn import file:///Users/dkelly/SVNROOT/test -m "New Project" > 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). Client-server is a *strength* not a weakness, it allows a surrogate process to manage access rights between multiple users. But contrary to your claims requires no additional effort for single-user use. A single user would never know subversion spawned other processes without looking hard. -- David Kelly N4HHE, [email protected] ======================================================================== Whom computers would destroy, they must first drive mad. -- 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>
