Yes, in fact, the real issue here is mergability, not binariness. It can be
argued that PostScript and XML are not truly mergable by CVS standards even
though they are not binary.
I also think that the "reserved" edit patches are good enough to handle
non-mergable file formats.
The ideal would be if CVS allowed pluggable diff and merge engines, and adopted
the "reserved" edit patches. Oh yeah, and the separation of physical filename
and archive filename that Paul had mentioned.
Noel
[EMAIL PROTECTED] on 2000.12.29 09:48:40
To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
cc: (bcc: Noel L Yap)
Subject: Re: Proposal to fix CVS binary file implementation
"Derek R. Price" wrote:
> There is the example of, say, GIF to JPEG. That could be considered mergable
with
> a proper tool.
Perhaps *.doc and RTF is a better example. What an automated merge tool would
do is
more obvious.
Derek
--
Derek Price CVS Solutions Architect ( http://CVSHome.org )
mailto:[EMAIL PROTECTED] OpenAvenue ( http://OpenAvenue.com )
--
I will not call the principal "spud head".
I will not call the principal "spud head".
I will not call the principal "spud head"...
- Bart Simpson on chalkboard, _The Simpsons_
_______________________________________________
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 & Co. Incorporated, its
subsidiaries and affiliates.
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
