Git has provision for using a consistent line ending in the repository but switching to the local platform's line ending (for what are recognized as text files) when unpacking a clone into local folders.
If a source-release clone is Zipped on a local machine, that Zip will have whatever line-endings are found in the local folders. Could that be a factor in the problem being noticed here? - Dennis -----Original Message----- From: jan i [mailto:[email protected]] Sent: Friday, August 14, 2015 11:03 To: [email protected] Subject: Re: [PRE-VOTE] Release candidate 0.1 On 14 August 2015 at 19:53, Peter Kelly <[email protected]> wrote: > Hi Jan, > > I just tried this version and all none of the tests fail. A quick look at > some of the files shows they’re now using Windows line endings (\r\n), > instead of Unix line endings (\n). The test code doesn’t handle this. It > should, but also the files should have remained in Unix line format after > they were moved. > problem exist on master as well, just checked. I will try and find out why. rgds jan i. [ ... ]
