[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Future CVS Development

From: Noel L Yap
Subject: RE: Future CVS Development
Date: Tue, 19 Jun 2001 13:49:59 -0400

>> -----Original Message-----
>> From: Kostur, Andre [mailto:address@hidden
>> > -----Original Message-----
>> > From: Noel L Yap [mailto:address@hidden
>> >
>> > CVS only requires files to be mergable.  This has a different
>> > meaning from
>> > requiring files to be non-binary.
>> >
>> > One thing that may be done is to add a hook for pluggable
>> > diffing/merging
>> > engines.
>As discussed before, this would require at least an extension to the
>RCS file format.

I don't think CVS was designed to be bound to RCS.

>> Now, pluggable engines would be truly cool!  I know that one
>> large argument
>> against CVS here (my office) was that it doesn't do
>> "intelligent" things
>> with proprietary format non-mergable files (like MSWord
>> documents), where
>> other source control systems can do (the counterexample was always
>> Clearcase).  But if you could plug in a diff/patch tool for
>> *.doc files,
>> (and perhaps a different diff/patch tool for *.ppt, another
>> for *.xls) that
>> would make these files mergable, and thus behave sensibly in CVS! :)
>Because of the above, you'd probably need one diff/patch tool for
>every file format, and you'd need to keep the diff/patch tools
>steadily updated for changes in file formats (MS Word file formats
>come to mind as changeable).  This is in contrast to the diff/patch
>standard in CVS, which applies to a large number of different sorts
>of files, and can remain unchanged.  I'm not sure producing diff/patch
>tools for arbitrary file formats is reasonable to expect out of an
>open source project.

Yes, of course.  All I would expect is to be able to use a provided hook.  I
wouldn't expect for CVS to supply the tools.


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.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]