On 11/28/2013 6:35 AM, Philippe Vaucher wrote:
I think the basic issue is that in SVN when one checks out a text file from the repository, line endings are converted from whatever they are in the repository to whatever the OS normally uses; for Windows CR-LF, for Linux LF. SVN does not think that the file has been changed because of this. Then when one commits a file in SVN the line ending is changed back to whatever it was originally in the SVN repository when it is put back in the repository.
One would like git to work the same way. I have no idea whether it does or not. But it seems irrelevant from my point of view what the line endings are in a repository as long as when I work on a file locally from a git repostory the line endings are correct for the OS I am on and git does not think there is some change just because the line endings in the repository and the line endings in the file locally are different. I hope git can accomplish this in some way, whether through some local settings or whatever.
Do people really want this behavior? It looks so hacky/kludgy to me. I mean, nowadays all editors can happily edit files with LF or CRLF and save them that way too. What do you gain from that behavior, except extra configuration of the tools and more headaches? I understand from where this feature comes from, back in the days where editors couldn't handle different line endings, but this is not the case anymore.
Please stop acting as if this is not an issue. Your naivete about how tools, whether on Windows, Linux, or Macintosh work with any type of line endings is just wrong. Sure it would be nice if this was not an issue, but that is not reality.