title: A sane way to rename a directory in subversion working copy
body: <p>While somehow versed in VCS (regular svn, git and git-svn user) I can't seem to wrap my head around this peculiar SVN behavior.</p>
  
  <p>Whenever I need to rename a directory in my SVN working copy from an otherwise 'clean' state - i.e <code>svn status</code> returns nothing and all other modifications have been commited - like so (which is what the svn doc suggests):</p>
  
  <pre><code>svn mv foo bar
  svn commit
  </code></pre>
  
  <p>SVN complains loudly:</p>
  
  <pre><code>Adding         bar
  Adding         bar/toto
  Deleting       foo
  svn: Commit failed (details follow):
  svn: Item '/test/foo' is out of date
  </code></pre>
  
  <p>As you wish:</p>
  
  <pre><code>svn update
  </code></pre>
  
  <p>Which gives:</p>
  
  <pre><code>   C foo
  At revision 46.
  Summary of conflicts:
    Tree conflicts: 1
  </code></pre>
  
  <p>There's a tree conflict, <em>while no third-party change happened</em>. Obviously, the only way to get out of this tree conflict mess is generically (from the svn red book):</p>
  
  <pre><code>svn resolve --accept working -R .
  svn commit
  </code></pre>
  
  <p>Renaming it remotely on the repo then updating my working copy seems quite braindead:</p>
  
  <pre><code>url=$(svn info | grep -e '^URL:' | sed 's/^URL: //') svn mv $url/foo $url/bar
  svn update
  </code></pre>
  
  <p>Is there a sanctioned, more streamlined way to rename a folder that I'm missing? What is the root cause behind that particularly surprising tree conflict state?</p>