Well, I had similar problems at a previous job with SourceSafe as I'm having with CVS. I totally "get" and understand the concept of these systems, but they're still overly headachey to use. Maybe I DONT really get them. hah. I understand mostly how they work and the concept but it seems like another case of "we don't need to make it easier because the people who use this are highly technical and they'll figure it out". Or as the gaming community might say "lrn2configure noob!"
For now, CVS works fine for us. But it still feels like we're using a go-cart with no engine. If we push it to the top of the hill, we can coast down the other side and even steer and stop if we want... but it feels incomplete usage and functionality-wise. Oh well, project for another day. Thanks for the input! -TG = = = Original message = = = On Wed, July 5, 2006 10:40 am, [EMAIL PROTECTED] wrote: > I don't know about you, Jay, but all we really want to do is keep a > record of revisions and be able to 'diff' between them and have the > files lock so if someone tries to open the file and it's already open, > that the user is alerted and allowed to open read-only if they desire. I *much* prefer the CVS/subversion paradigm of concurrent changes, but if the above is what you want, perhaps you should look into SourceSafe. NOTE: SourceSafe in the 80s on Mac PPC *ate* two of my projects when goofballs added ".doc" files as text. I'll never ever ever use this product again, no matter how many people tell me it's been fixed. YMMV ___________________________________________________________ Sent by ePrompter, the premier email notification software. Free download at http://www.ePrompter.com. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
