Concurrent editting of files can be avoided by using the available edit and
checkin patches but nothing exists (or can exist) for the situation with
branches.
So, if you can avoid concurrent editting of non-mergable files, then CVS is OK
to use.
Noel
|--------+----------------------->
| | |
| | [EMAIL PROTECTED]|
| | |
| | 07/11/2001 |
| | 04:31 PM |
| | |
|--------+----------------------->
>----------------------------------------------------------------------------|
| |
| To: [EMAIL PROTECTED] |
| cc: (bcc: Noel L Yap) |
| Subject: RE: How well does CVS handle other types of data? |
>----------------------------------------------------------------------------|
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
This communication is for informational purposes only. It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan Chase & Co., its
subsidiaries and affiliates.
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
