tisdag 28 april 2009 13:24:31 skrev Jakub Narebski <jnareb@xxxxxxxxx>: > Line endings (issue 8.) is in theory and in practice (at least for > Git) a non-issue. > > In theory you should use project's convention for end of line > character in text files, and use smart editor that can deal (or can be > configured to deal) with this issue correctly. Windows people will disagree. > In practice this is a matter of correctly setting up core.autocrlf > (and in more complicated cases, where more complicated means for git > very very rare, configuring which files are text and which are not). Which proves it is an issue or we wouldn't need to tune settings to make it work right. A non-issue is something that "just works" without turning knobs. I had had to think more than once on what the issue was and the right way to solve these issues. It can be considered wierd, because Eclipse on Linux generated files with CRLF which I happily committed and Git on Windows happily converted to LF and determined that the HEAD and index was out of sync, but refuesed to commit the CRLF>LF change becuase there was no "diff".. You know the fix, but don't tell me it's not an issue. -- robin -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html