info-cvs
[Top][All Lists]
Advanced

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

Re: CVS and Jar files: Should you import Jar into the Repository? Why or


From: Paul Sander
Subject: Re: CVS and Jar files: Should you import Jar into the Repository? Why or why not
Date: Tue, 5 Mar 2002 16:12:24 -0800

>--- Forwarded mail from address@hidden

>[ On Tuesday, March 5, 2002 at 22:01:01 (GMT), Richard Caley wrote: ]
>> Subject: Re: CVS and Jar files: Should you import Jar into the Repository? 
>> Why or why not
>>
>> If your only reason for using CVS is to get diffs, then you will think 
>> differently, but I would guess most people want versioning first and
>> diffs as a bonus.

>Versioning _is_ diffs!  There's no point to keeping every revision of
>every file unless you can calculate a _meaningful_ delta between them!
>Not even if your storage scheme is to keep each revision of the whole
>file as a unique object.

>CVS really Really REALLY MUST use text-based diff deltas to work even
>marginally succussfully, partly because it uses RCS, and partly because
>it practically (and by design) forces you to allow concurrent edits and
>thus forces you to do merges with 'patch'.

RCS stores binary files just fine, though perhaps not as efficiently as
most ASCII files.  All that is needed is that they come out bit-for-bit
identical to what went in for any given revision.

I've already proven that CVS can be modified to accomodate new data types
by integrating new merge tools, and still retain its concurrent editing
capabilities.

And it doesn't force anything with "patch".  We've already had this argument;
CVS falls back on something else if "patch" isn't available.

In other words, there's nothing holding us back at this point from just
fixing CVS so that it can accomodate the types of data that are used in
modern software development efforts.

>--- End of forwarded message from address@hidden




reply via email to

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