[Top][All Lists]

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

RE: How well does CVS handle other types of data?

From: Noel L Yap
Subject: RE: How well does CVS handle other types of data?
Date: Fri, 13 Jul 2001 10:47:35 -0400

>> Why, in the name of Babbage, is that supposed to be better?  I still
>> can't automatically merge binaries, so it's no advantage there.  So
>> what do I get if I do that?
>but you can't avoid having to do something equivalent to merging of
>opaque format binary files with CVS!

You can if you have proper procedures in place.  What you can't do is prevent
the situation (at least I haven't found a way).  But if no procedure can, then
no tool can.

>If you must handle non-mergable files as source, and you want to use CVS
>for your mergable source, then it makes almost infinite sense to store
>the non-mergable files in some other revision tracking system!!!!!!

No, it doesn't.

>-kb is not the solution -- it just makes the problem harder!  If it
>didn't exist in the first place you'd never have gotten into this

How does it make it harder (specially if you have procedures to back it up)?

>Why not just use RCS stand-alone for the binaries?  Making a build
>system that pulls a specified revision from an RCS file is trivial!

I didn't know RCS prevented branching :-}
>Why moan and complain about the impossible when a few tiny tweaks in the
>right placess will make all your problems easy to manage?

I haven't had any problems with non-mergable files (or, more correctly,
RCS-non-mergable files).


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]