Jeremy Hughes wrote:
This test was written initially to ensure none of our text files we check inhi,
had rogue ^M characters. Agreed it's probably dangerous because it has a
side effect. Some of us use the Eclipse dev environment ... the Windows
version which has a tendancy to add ^M eg when creating a new file.
i think in this case Eclipse may have been a culprit and not CVS...
http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-vcm-home/docs/online/cvs_features2.0/cvs-faq.html#10_3
This test was just to keep us honest as ^M can annoy non-windows developers.CVS handles automatically end of line translations so there is no need to fix them.
alek
--
The ancestor of every action is a thought. - Ralph Waldo Emerson