title: Why is GIT deleting all branches of a cloned SVN repo after running git fetch -p origin?
body: <p>I cloned an SVN repository using <code>git svn clone --stdlayout</code>. After cloning the repository I cleaned it up using the <a href="https://www.atlassian.com/git/tutorials/migrating-convert/" rel="nofollow">atlassian migration script</a>: </p>
  
  <pre><code>java -Dfile.encoding=utf-8 -jar ~/svn-migration-scripts.jar clean-git 
    --force.
  </code></pre>
  
  <p>Then I set the new remote and pushed the repository to the new remote GIT server using <code>git push --all origin</code></p>
  
  <p>After trying to clean up some more I also ran <code>git fetch -p origin</code> but that deletes <strong>all</strong> original SVN branches:</p>
  
  <pre><code> ...
   x [deleted]         (none)     -&gt; origin/release_II
   x [deleted]         (none)     -&gt; origin/release_III
   ... etc
  </code></pre>
  
  <p>Is this normal for cloned SVN repositories? It seems like the original SVN branches are not real branches in the new GIT repository. Did I forget something during the migration process? The prune command seems very hard to undo. How can we make sure we don't loose these branches if we run (maybe by accident) a similar command in the future?</p>