title: Should I check in `.ruby-gemset` and/or `.ruby-version`?
body: <p>I've just updated RVM, and in place of the old <code>.rvmrc</code>, it auto-created <code>.ruby-gemset</code> and <code>.ruby-version</code>.</p>
  
  <p>I've always had <code>.rvmrc</code> files with contents like <code>rvm use --create default@project_name</code>. However, <code>.ruby-version</code> contains the specific Ruby version I'm running rather than <code>default</code>. I'm hesitant to check this in.</p>
  
  <p>Also, I heard someone say on a podcast that one shouldn't check in <code>.ruby-gemset</code> because others may have their own preferences about how to name gemsets.</p>
  
  <p><strong>When should or shouldn't I check in <code>.ruby-gemset</code> and/or <code>.ruby-version</code>?</strong></p>
  
  <p>Specifically:</p>
  
  <ul>
  <li>What are some of the tradeoffs? </li>
  <li>How does the type of project affect the decision (for example, applications vs gems)?</li>
  <li>If they should be checked in, how does the type of project affect what should go in these files?</li>
  </ul>
  
  <p>Citations from from the creators of tools like rvm, rbenv, etc would be appreciated in an answer.</p>