RE: Re: Disabling automatic conflict resolution?

>> Or put on your Carl Sagan voice: "*billions* of users have been using
>> CVS for years, and have had no problems with this..."

I just have to jump in and say, how many of those billions of users have
been keeping primarily *binary* files in CVS? If CVS is a poor tool for
a job, then people won't generally use it for that job.

CVS is a good tool for shared editing of text files, and ok for storage
of binary files that are edited as a whole (eg who would want to merge
changes to a JPG?). It's near useless for shared editing of binary files
because it can't prevent two people modifying the same file
simulataneously, and unless there is some system to merge the results

To take my own example, I suspect few if any Visual Foxpro developers
are keeping their source code in CVS. We're stuck with VSS because it
can do locks (ignoring at the moment that VFP integrates using the
Microsoft SCC API which is hard to emulate). VFP is actually rather
cool the way it keeps source code in database tables, but it does make
source control difficult.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Aug 18 23:57:38 2003