You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By default, git on Windows is configured to convert to Unix line endings when pushing the code and to convert back to Windows line endings when pulling the code. However, for some reason this repository has Windows line endings (perhaps because you have an unusual git configuration), which means that anybody who checks out the code on a Unix platform will have to deal with Windows line endings (typically by running the dos2unix program on every project file, which is what I did).
Normally I wouldn't care what line endings a project is written in if I'm just using the project as a dependency. However, the purpose of this project is to be forked and modified, in which case the line endings matter because the code is designed to be modified.
The text was updated successfully, but these errors were encountered:
I think I have changed this now in 0156796, although I am not quite sure how this happened in the first place. As far as I can tell, git on my Windows machine is configured to covert to LF automatically (core.autocrlf is set to true)
By default,
git
on Windows is configured to convert to Unix line endings when pushing the code and to convert back to Windows line endings when pulling the code. However, for some reason this repository has Windows line endings (perhaps because you have an unusualgit
configuration), which means that anybody who checks out the code on a Unix platform will have to deal with Windows line endings (typically by running thedos2unix
program on every project file, which is what I did).Normally I wouldn't care what line endings a project is written in if I'm just using the project as a dependency. However, the purpose of this project is to be forked and modified, in which case the line endings matter because the code is designed to be modified.
The text was updated successfully, but these errors were encountered: