Switch to UNIX/LF line endings?

[akien-mga]

The repo currently uses DOS/CRLF line endings which are the default on Windows, but a hassle on UNIX systems (macOS/Linux/*BSD).

To handle this in cross-platform projects, the convention is usually to use UNIX/LF line endings.
On Windows, Git will by default automatically convert the LF to CRLF when pulling, and convert back to LF when pushing, so that's transparent to Windows developers.

This is a good read by a GitHub developer on that matter.

I'm opening this issue to ask whether you'd consider switching to LF in this repo. If so, I can make a PR with the relevant changes and corresponding .gitattributes file to ensure it works fine for all.

[castano]

I don't have strong opinion one way or the other. I generally have my editors autodetect line endings, so I just maintain whatever line ending was used when the file was created. Do you know how would this affect the svn bridge? I only know git basics, so I prefer using svn as the front end.

…

On Fri, Dec 15, 2017 at 12:26 PM, Rémi Verschelde ***@***.***> wrote: The repo currently uses DOS/CRLF line endings which are the default on Windows, but a hassle on UNIX systems (macOS/Linux/*BSD). To handle this in cross-platform projects, the convention is usually to use UNIX/LF line endings. On Windows, Git will by default automatically convert the LF to CRLF when pulling, and convert back to LF when pushing, so that's transparent to Windows developers. This is a good read <http://adaptivepatchwork.com/2012/03/01/mind-the-end-of-your-line/> by a GitHub developer on that matter. I'm opening this issue to ask whether you'd consider switching to LF in this repo. If so, I can make a PR with the relevant changes and corresponding .gitattributes file to ensure it works fine for all. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#12>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAhcM0eo7Y8z-JdcM3uHx8K4Le32mNf7ks5tAtXggaJpZM4RD9kA> .

-- Ignacio Castaño [email protected]

[castano]

Also, note that I'm leaving on vacations tonight and may not be able to review/merge code until January 2nd.

…

On Fri, Dec 15, 2017 at 2:58 PM, Ignacio Castaño ***@***.***> wrote: I don't have strong opinion one way or the other. I generally have my editors autodetect line endings, so I just maintain whatever line ending was used when the file was created. Do you know how would this affect the svn bridge? I only know git basics, so I prefer using svn as the front end. On Fri, Dec 15, 2017 at 12:26 PM, Rémi Verschelde < ***@***.***> wrote: > The repo currently uses DOS/CRLF line endings which are the default on > Windows, but a hassle on UNIX systems (macOS/Linux/*BSD). > > To handle this in cross-platform projects, the convention is usually to > use UNIX/LF line endings. > On Windows, Git will by default automatically convert the LF to CRLF when > pulling, and convert back to LF when pushing, so that's transparent to > Windows developers. > > This is a good read > <http://adaptivepatchwork.com/2012/03/01/mind-the-end-of-your-line/> by > a GitHub developer on that matter. > > I'm opening this issue to ask whether you'd consider switching to LF in > this repo. If so, I can make a PR with the relevant changes and > corresponding .gitattributes file to ensure it works fine for all. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <#12>, or mute the thread > <https://github.com/notifications/unsubscribe-auth/AAhcM0eo7Y8z-JdcM3uHx8K4Le32mNf7ks5tAtXggaJpZM4RD9kA> > . > -- Ignacio Castaño ***@***.***

-- Ignacio Castaño [email protected]