[Martin v. Löwis]
> Last I tried, VS 2003 would tolerate \n line endings in vcproj files
> (these being plain XML files). I don't remember whether it would
> tolerate them in .sln files (as these are *not* XML files); this is
> why the .sln file is set to binary.
FYI, I tried changing pcbuild.sln
Tim Peters wrote:
>>Should 'sln' and 'vcproj' be added to the extensions list? I think these are
>>text-files too. Although PCBuild\pcbuild.sln has a binary mime-type property,
>>so the script would not change that.
>
>
> I don't know whether they're text files in the SVN eol-style "native"
> s
Tim Peters wrote:
> [Thomas Heller]
>> ...
>> The Linux-head is the release manager, prepaing the release on
>> a unixish platform, in combination with the windows guy who downloads
>> the source distribution and tries to compile that on Windows.
>
> That sounds like an artificial (process-created
[Thomas Heller]
> ...
> The Linux-head is the release manager, prepaing the release on
> a unixish platform, in combination with the windows guy who downloads
> the source distribution and tries to compile that on Windows.
That sounds like an artificial (process-created) problem, then. Since
a re
Tim Peters wrote:
> [Tim Peters]
>>> Added:
>>>python/trunk/Tools/scripts/svneol.py (contents, props changed)
>>> Log:
>>> Simple utility to add svn:eol-style to text files under
>>> SVN control. Like reindent.py, I expect to run this
>>> mindlessly from time to time, checking in whatever it
[Tim Peters]
>> Added:
>>python/trunk/Tools/scripts/svneol.py (contents, props changed)
>> Log:
>> Simple utility to add svn:eol-style to text files under
>> SVN control. Like reindent.py, I expect to run this
>> mindlessly from time to time, checking in whatever it
>> happens to do ;-)
[Th
