title: How to properly handle a discontinuity in git-svn
body: <p>I am in a situation where (say) commit 666 is dodgy, i.e</p>
  
  <pre><code>git svn clone [REPO] -r665 #works
  git svn clone [REPO] -r666 #Malformed XML
  git svn clone [REPO] -r667 #works
  </code></pre>
  
  <p>but even weirder</p>
  
  <pre><code>git svn clone [REPO] -r665
  cd [REPO_NAME]
  git svn fetch -r667 #Malformed XML
  git svn fetch -r668 #Malformed XML
  git svn fetch -r669 #Malformed XML
  ...
  </code></pre>
  
  <p>(this also happens with analogous commands in SVN)</p>
  
  <p>currently, the only way I know around this is either</p>
  
  <ul>
  <li>forgo having any history before r666</li>
  <li>using 2 svn repos pointing to the same remote and hacking around with rebase/cherry pick</li>
  </ul>
  
  <p>Is there a more proper way to do this?</p>