I believe that what some people need with respect to a version control
system, is to be able to manage binary files in addition to
traditional text files.
For text files, there's no problem, CVS is perfect with its concurrent
abilities.
For binary files, CVS is somewhat lacking.
Well, it's probably not a good response to propose to use a different
version control system for binary files while using CVS for text file,
is it.
Therefore, it may be a good idea to have a version control system
working with two different paradigms:
- do concurent versionning for text files,
- do file locking, non concurrent versionning for binary files.
Name it CXLVS (Concurrent XOR Locking Versionning System).
Otherwise, the alternative is to separate text files from binary
files, and to manage text files with CVS and binary files with another
versionning system. Not tastful...
--
__Pascal_Bourguignon__ (o_ Software patents are endangering
() ASCII ribbon against html email //\ the computer industry all around
/\ and Microsoft attachments. V_/ the world http://lpf.ai.mit.edu/
1962:DO20I=1.100 2001:my($f)=`fortune`; http://petition.eurolinux.org/
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCS/IT d? s++:++(+++)>++ a C+++ UB+++L++++$S+X++++>$ P- L+++ E++ W++
N++ o-- K- w------ O- M++$ V PS+E++ Y++ PGP++ t+ 5? X+ R !tv b++(+)
DI+++ D++ G++ e+++ h+(++) r? y---? UF++++
------END GEEK CODE BLOCK------
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
