If you've ever seen the following in your command prompt window then you understand my frustration.
This can be easily solved by typing the following into your command prompt.
git config --global core.autocrlf false
This tells Git to just go with the flow and not start modifying files, or so I thought. Turns out this issue has crept back for Visual Studio 2013 developers.
Visual Studio 2013 introduces first class support for Git. This support for Git brings along with it the .gitattributes file. If you look into your solution folder you will find it. Open the file up and what do you see?
Aaaaaaargh! This one line can cause tremendous chaos, and I am not sure why it is set to "auto" to begin with. The common practice for developers is to have this value set to false so that when contributing to other projects you don't accidentally modify every file in the entire project.
Change the one line to your global setting and you should nip this nasty problem in the butt.