[Top][All Lists]

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

Re: Coflict marker detection proposal

From: Noel L Yap
Subject: Re: Coflict marker detection proposal
Date: Tue, 17 Jul 2001 18:02:30 -0400

Oh yeah, I never got a legitimate response as to why developers who really want
to block such commits can't use commitinfo scripts to do so.


[ 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.)

                                   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]