title: Subversion: prevent local modifications to one file from being committed?
body: <p>I have a Subversion working copy where I made some local modifications to one file. The modifications are only relevant to me, I do not want to commit them. (The version in the repository contains some default values which are suitable for the other users, just not for me, which is why I want to override them locally.)</p>
  
  <p>Note that although I do not want to commit my changes, I <em>do</em> want to receive any updates made in the repository when I do <code>svn update</code>. Also, it is only in my working copy that I do not want to commit the changes to that file, the other users should not be affected. So <code>svn:ignore</code> or commit hooks do not fit my purpose.</p>
  
  <p>Currently, I simply do:</p>
  
  <pre><code>svn commit file1 file2...
  </code></pre>
  
  <p>where I specify explicitly the files that have changes <em>excluding</em> the particular file that I do not want to commit.</p>
  
  <p>However, while I'm working, I have the habit of simply writing:</p>
  
  <pre><code>svn commit -m "Log of what I just did"
  </code></pre>
  
  <p>and I fear that I will inadvertently commit the "forbidden" file by using the above command at a moment when I'm not attentive.</p>
  
  <p>In short, what I'm looking for is simply a way of "marking" a file in a working copy which prevents Subversion from committing the changes in that file (it doesn't have to be automatic exclusion, even if I just get an error when I try to commit all files, it is fine). Sort of like marking files in a "conflict" state...</p>
  
  <p>Does such a thing exist?</p>
  
  <p><strong>Update</strong>: akent, thanks for pointing out this <a href="https://stackoverflow.com/questions/635446/svn-is-there-a-way-to-mark-a-file-as-do-not-commit">very similar question</a>.</p>