A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2000-August/008198.html below:

[Python-Dev] *.dsp and *.dsw are treated by CVS as binary. Why?

[Python-Dev] *.dsp and *.dsw are treated by CVS as binary. Why? [Python-Dev] *.dsp and *.dsw are treated by CVS as binary. Why?Guido van Rossum guido@beopen.com
Fri, 11 Aug 2000 17:56:23 -0500
> These files (PCbuild/*.dsw PCbuild/*.dsp) are just normal text files. Why,
> then, do we treat them as binary files.

DevStudio doesn't (or at least 5.x didn't) like it if not all lines
used CRLF terminators.

> Would it not be preferable to have those files be handled like a normal text
> files, i.e. check it out on Unix and it uses Unix line terminators, check it
> out on Windows and it uses DOS line terminators.

I think I made them binary during the period when I was mounting the
Unix source directory on a Windows machine.  I don't do that any more
and I don't know anyone who does, so I think it's okay to change.

> This way you are using the native line terminator format and text processing
> tools you use on them a less likely to screw them up. (Anyone see my
> motivation?).
> 
> Does anybody see any problems treating them as text files? And, if not, who
> knows how to get rid of the '-kb' sticky tag on those files.

cvs admin -kkv file ...

--Guido van Rossum (home page: http://www.pythonlabs.com/~guido/)



RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4