title: How should I configure git line endings for non Windows hosts with Windows VMs?
body: <p>We develop on Windows and use git. Locally, line endings are CRLF and all the magic in between means that the files on our production server (CentOS) will have LF. Everyone is happy.</p>
  
  <p>We also use a Windows only tool to generate a LOT of the files for us (PHP Maker). This app generates files with Windows line endings.</p>
  
  <p>Still all good.</p>
  
  <p>But, we have 2 non Windows developers (one on a Mac, one on Ubuntu Mate). For the non PHP Maker generated files, their editors work with files that have their OS specific line endings and all the magic in between means that those files end up with the correct line endings on our production server. And when the Windows developers interact with the non PHP Maker files, it is still all good with CRLF line endings locally.</p>
  
  <p>Everything seems fine.</p>
  
  <p>Right up to the point where the non Windows developers have to run the PHP Maker application in their Windows VM on their Mac/Ubuntu machines.</p>
  
  <p>Then things seem to go a little wonky.</p>
  
  <p>The net effect is that when these developers run PHP Maker and commit from their development machines (not the VM), the line endings seem to get ... confused ... and somehow when the windows developers get hold of these files, they are 100% whitespace different - and it is JUST line endings.</p>
  
  <p>I'm willing to do research but I don't know enough to work this out as I am only on Windows (where it all just works as expected) and don't have access to the Mac/Ubuntu setups to diagnose the issue.</p>
  
  <p>So. What am I supposed to do? We have no issue enforcing things one way or the other (as in "for good or bad, this is how we want things setup").</p>
  
  <p>But some ideas, suggestions, recommendations, perfect answers, etc. are all appreciated.</p>
  
  <p>Regards,</p>
  
  <p>Richard Quadling.</p>