The difference is that CVS is an excellent tool for managing source code,
because the VAST majority of cases involving concurrent editing of source
code is automatically mergable, and in the case of conflicts it is easy to
mark the differences between the files to make it easy to fix by hand. CVS
is a poor tool for managing images, because concurrent editing of binary
files such as images should always be avoided.

There could be hooks for handling mergable binary formats, but at that point
I think a tool other than CVS would be more appropriate.

> -----Original Message-----
> From: Noel L Yap [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, July 11, 2001 4:23 PM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: RE: How well does CVS handle other types of data?
>
>
> What's the difference?  In either case you'll have to handle the
> merge on your
> own.
>
> What about binary files for which there already exists a merge
> algorithm (eg
> Word docs)?


_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

Reply via email to