Git, jME and line endings

Development
1

I think we should do something regarding line endings in our git repos. Problem is windows is using CRLF and Linux and moden OSX uses LF as line ending.

Git is going to be sad (and our history cluttered) if we do not decide on what we should do about this.

2

/sigh this? 2014? I guess setting the global gitinfo is the best way to go.

3

^^ Also make sure not some win fag pushes cp1252 encoded sources :stuck_out_tongue:

4
@Empire Phoenix said: ^^ Also make sure not some win fag pushes cp1252 encoded sources :P

Hey! I use cp1252 on everything… my code, my coffee, as bath salts. It not only tastes like the original… but there are fewer calories. This isn’t just for fags anymore… metrosexual developers around the globe are using it daily now.

5

Well either cp1252 does stand for something else, your someone got mad, java it utf8 it makes no sense to code in something else.

6

If a windows user setup GIT properly, it should have been to use cr/lf when checking out but commit as LF.

Source control should always have text files stored with LF as the line endings. Clients can then convert as needed.

…such was the way with CVS, such was the way with SVN, and such should be the way with GIT. Since I just installed GIT on one of my boxes recently, I know this was an option. If the netbeans version doesn’t do this by default then I think it’s kind of broken if it’s checking things in with cr/lf.

7

There is 826 files with CRLF line terminators inside our repo… I think we wanna fix that and maybe commit a .gitattributes file to make sure everybody uses the same configuration.

List of files with bad line terminators:

8
@kwando said: There is 826 files with CRLF line terminators inside our repo... I think we wanna fix that and maybe commit a .gitattributes file to make sure everybody uses the same configuration.

List of files with bad line terminators:
Files with CRLF · GitHub

Agreed.