Re: Coflict marker detection proposal

[Noel L Yap]

>[ On Tuesday, July 17, 2001 at 11:13:30 (-0700), Lan Barnes wrote: ]
>> Subject: Re: Coflict marker detection proposal
>>
>> For this practical reason I believe that it's important for CVS to allow
>> commits of files that contain textual examples of conflict markers. I would
>> be interested in the counter arguments of anyone feeling my argument has no
>> validity.
>
>You'll find lots of textual examples of conflict markers in the CVS
>documentation, yet none of them are visible as real conflict markers in
>the source for that documentation.
>
>Even if the documentation were not in TeXinfo format, but instead just
>in plain ASCII text format, it would still be impossible to even concoct
>a reason why those marker examples would have to appear in such a way
>that they would be seen by CVS as real conflict markers.  It's unlikely
>that even without creating a fake example that such a file would ever
>encounter a problem.
>
>(Yes there is a generic problem with *.info* files (and perhaps other
>potential forms of formatted documentation), but they're not source
>files now are they!  Even then a tiny and insignificant change to the
>makeinfo output would avoid the problem forever.)

Doesn't this depend on how the info files were created?  If people are
maintaining them with text editors, then they most certainly are source files.
Or are you now going to argue that since they can be generated, that they must
not be source files?

There are now four people against your proposal, one of whom has done the search
you asked for and found files matching your original criteria, and one person
for your proposal.  When are you going to accept the fact that this doesn't
belong in the distribution (at least not without a simple workaround -- I prefer
"cvs ci -f" myself)?

Noel




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.