I recently found some files line endings borked on linux ( touched with windows ? )
I suggest adding * text=auto to .gitattributes
Line endings
Re: Line endings
It is the default as far as I rememberjensverwiebe wrote: ↑Thu Feb 22, 2018 11:29 am I recently found some files line endings borked on linux ( touched with windows ? )
I suggest adding * text=auto to .gitattributes
I had exactly the opposite problem with Git replacing CR/LF in .ply (binary format) and corrupting the files. So I had to add https://github.com/LuxCoreRender/LuxCor ... attributes to consider .ply binaries.
-
- Supporting Users
- Posts: 141
- Joined: Tue Jan 09, 2018 6:48 pm
Re: Line endings
Okay, seems * text=auto can be avoided.Dade wrote: ↑Thu Feb 22, 2018 11:58 amIt is the default as far as I rememberjensverwiebe wrote: ↑Thu Feb 22, 2018 11:29 am I recently found some files line endings borked on linux ( touched with windows ? )
I suggest adding * text=auto to .gitattributes
I had exactly the opposite problem with Git replacing CR/LF in .ply (binary format) and corrupting the files. So I had to add https://github.com/LuxCoreRender/LuxCor ... attributes to consider .ply binaries.
I configured my git as per: https://help.github.com/articles/dealin ... e-endings/
with git config --global core.autocrlf input
Now my diffs look okay with fresh clone.