At .gitattributes kill all text auto conversions about bc-java HOT 3 CLOSED

We are following roughly the advice here: https://help.github.com/articles/dealing-with-line-endings . There were recently a few java files in the repository with CRLF endings; they have been fixed. We expect the repository itself to contain only LF endings. If you are working on Windows, I advise you to set core.autocrlf = true, and perhaps core.eol = crlf (even though it should be the default) since there appear to still be some git clients that fail to choose the native EOL correctly when text=auto is set in .gitattributes .

from bc-java.

My desktops are Fedora 18 Linux, but still somehow the system is very much confused of what kind of line endings it should do. Actually I personally hate the idea that source repository "knows" what format files should be.
I have never seen it working properly.

from bc-java.

Take a look at https://help.github.com/articles/dealing-with-line-endings#re-normalizing-a-repository : really you should only need to remove the affected files and reset. Let me know if your tree still has problems once you've reset it.

As to the substance of this issue, we will be sticking with the .gitattributes for the moment. It's working fine for us internally across Linux and Windows (once we sorted out some teething problems). We are fairly new to git, but from everything I've read about it, this has become the standard way to handle it. That file doesn't actually compel clients to do anything, it merely advises them of the conventions for this repository.

from bc-java.