![]() And for most users this should be the case. How about requiring not to have autocrlf at false for CS instead? For the result in the repository this would mean the same whether it is set to true or input, which is line endings in the repository are LF. #JEDIT SETUP LINE ENDINGS WINDOWS#You could (should?) actually also add another build job that runs with autocrlf set to input or false on the Windows build machines to make sure it stays like that in the future. With the changes I propose, the tests work properly on Windows, whether someone has linux line endings or windows line endings doesn't matter anymore. And for most users this should be the case anyway. With this the problem of course does not happen.īut I'd suggest to instead fix these incompatibilities in the tests and then maybe require instead not to have autocrlf at false for CS instead? For the result in the repository this would mean the same whether it is set to true or input, which is line endings in the repository are LF. In #6511 mentioned that the website of CS requires to use autocrlf with true. I have globally set autocrlf to input just to remind me to change line ending to LF if I have it at CRLF accidentally on some file, but I don't like to have Git automatically change line endings on checkout, besides that it wastes space on my local disk. I personally hate it when a VCS mangles files automagically. The CS tests assume that on Windows the files have Windows line endings. If Git is used without modifying line endings on checkout (e. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |