 <h1>Check which svn commit caused the problem.</h1> <p>The commits are outputted by the <code>git svn clone</code> command, preceded by an <em>r</em>. The last commit that is outputted is the problematic one.</p> <p>The next example shows what the <code>git svn clone</code> command outputs when begin procesing the <strong>Subversion revision</strong> <code>15</code> as the <strong>Git commit</strong> <code>373fb1...</code>:</p> <pre><code>r15 = 373fb1de430a6b1e89585425f276aae0058c3deb (refs/remotes/svn/trunk) </code></pre> <h1>Split up the <code>git svn clone</code> command using the <code>-r</code> (revision) option</h1> <p>Use this method:</p> <pre><code>git svn clone -r 0:&lt;problematic_revision - 1&gt; &lt;repo URL&gt; git svn clone -r &lt;problematic_revision - 1&gt;:problematic_revision &lt;repo URL&gt; git svn clone -r &lt;problematic_revision&gt;:HEAD &lt;repo URL&gt; </code></pre> <p>Supposing the revision <code>15</code> as the problematic one, and the repo in <code>/tmp/svn/repo/</code>, the solution would be:</p> <pre><code>git svn clone -r 0:14 file:///tmp/svn/repo/ git svn clone -r 14:15 file:///tmp/svn/repo/ git svn clone -r 15:HEAD file:///tmp/svn/repo/ </code></pre>