title: Renaming a folder and not losing the link between the branch and the trunk
body: <p>I had two working copies: of a trunk and of a branch:</p>
  
  <ul>
  <li>trunk -> App 1.0</li>
  <li>branches -> 1.2 -> App 1.0</li>
  </ul>
  
  <p>I needed to rename <code>App 1.0</code> to <code>Application</code> ("1.0" being an archaism from the days where versioning was done "manually" and SVN was underused to put it mildly; I'm trying to set it right now, although I haven't had much experience with source control).</p>
  
  <p>I did <code>TortoiseSVN -&gt; Rename</code> on my <code>1.2\App 1.0</code> and <code>trunk\App 1.0</code> local disk folders (working copies), and I renamed the folders in the repository as well (via the <code>Repo-browser</code>).</p>
  
  <p>And yet code file <code>abc.cs</code> in the 1.2 branch still "thinks" that its base is the old file: <code>App 1.0/abc.cs</code>.</p>
  
  <p><code>Diff with previous version</code> gives me an error (<em>"Subversion reported an error: Unable to find repository location for 1.2\App 1.0\abc.cs in revision 604"</em>). </p>
  
  <p>See the revision graph for this file:</p>
  
  <p><img src="https://i.stack.imgur.com/S40xV.jpg" alt="enter image description here"></p>
  
  <p>(I edited out the actual name of the application for reasons easy to understand.)</p>
  
  <p>Propagating trunk modifications by merging them into the branch is now a bit troublesome.</p>
  
  <p>What's more, my collegue still has an <code>App 1.0</code> working copy (hasn't comitted nor updated it yet), so I'm somewhat afraid that we're about to mess things up, and I'm not sure how to go on from here.</p>
  
  <p><strong>The question is:</strong> where did I do wrong, and how do I fix that (both for me as well as my collegue)?</p>
  
  <p>I guess that renaming both folders independently was the mistake that broke history tracing (no direct connection between 637 and 639 on the picture now, while that's what I would need); I'm just not sure what I should have done instead, and neither how to fix it.</p>