Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm collaborating on a Git project that has developers on OSX, Linux and Windows. I've set my autocrlf setting to auto which means that it converts the line endings to CRLF as it pulls them down to my Windows system and then should commit them with LF. However, my IDE (Netbeans) doesn't respect the autocrlf setting and commits them with CRLF still which causes problems for the deployment server and other users.

I'm tempted to just leave the files in LF on my Windows system as that doesn't seem to cause any problems. I'm wondering what I'm missing that makes it important to convert to CRLF? My IDE, text editor (UltraEdit), apache and other relevant tools appear to cope with LF just fine.

To summarise, why bother converting to CRLF for windows?

share|improve this question
up vote 3 down vote accepted

You'll need to convert to CR/LF only for software that does not understand LF line editings. Virtually all software oriented towards software development will support unix-style line endings natively, the only trouble you'll run in to will be the Windows command line and a few programs that are distributed with Windows.

share|improve this answer
Like Notepad. Which you shouldn't be using anyways. – Ignacio Vazquez-Abrams Jul 3 '11 at 1:12
Thanks, I use UltraEdit, so no dramas there. – Jonathan Day Jul 4 '11 at 12:59

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.