title: What to put under version control?
body: <p>Almost any IDE creates lots of files that have nothing to do with the application being developed, they are generated and mantained by the IDE so he knows how to build the application, where the version control repository is and so on.</p>
  
  <p>Should those files be kept under version control along with the files that really have something to do with the aplication (source code, application's configuration files, ...)?</p>
  
  <p>The things is: on some IDEs if you create a new project and then import it into the version-control repository using the version-control client/commands embedded in the IDE, then all those files are sent to the respitory. And I'm not sure that's right: what is two different developers working on the same project want to use two different IDEs?</p>
  
  <hr>
  
  <p>I want to keep this question <strong>agnostic</strong> avoiding references to any particular IDE, programming language or version control system. So this question is not exactly the same as these:</p>
  
  <ul>
  <li><a href="https://stackoverflow.com/questions/191533/svn-and-binaries">SVN and binaries</a> - but this talks about binaries and SVN </li>
  <li><a href="https://stackoverflow.com/questions/421880/do-you-keep-your-build-tools-in-version-control">Do you keep your build tools in version control?</a> - but this talks about build tools (e.g. putting the jdk under version control)</li>
  <li><a href="https://stackoverflow.com/questions/186196/what-project-files-shouldnt-be-checked-into-svn">What project files shouldn’t be checked into SVN</a> - but this talks about SVN and dll's</li>
  <li><a href="https://stackoverflow.com/questions/116121/do-you-keep-your-project-files-under-version-control/119377">Do you keep your project files under version control?</a> - very similar (haven't found it before), thanks VonC</li>
  </ul>