[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: Mon, 16 Jul 2001 10:03:48 -0400

I think a proper patch to this would be to use hashes as well (or in lieu of)
timestamps.  The hashes possibly can be cached to speed up comparisons.

CVS should not be looking for conflict markers:
1.  Doing so will tie in the diff3 even more than it is now.
2.  It will prevent checkin of files that legitimately contains the markers, not
catch real conflicts in such files, or introduce new markers to mark the
instances of conflict markers that CVS should ignore.

If developers want to prevent files with conflict markers from being checked in,
they can use commitinfo to do so.


[ On Saturday, July 14, 2001 at 11:52:48 (-0700), Mike Castle wrote: ]
> Subject: Re: How well does CVS handle other types of data?
> Except that CVS doesn't continue to detect conflicts.  A simple touch(1) of
> the file is sufficient to mark the file as "fixed."  And that will work on
> any file type.

I think I've finally fixed that bug in the version I use.  I'll post
patches once I've tested a bit more.....

                                   Greg A. Woods

+1 416 218-0098      VE3TCP      <address@hidden>     <address@hidden>
Planix, Inc. <address@hidden>;   Secrets of the Weird <address@hidden>

Info-cvs mailing list

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]