Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>If you don't need the branches, try:</p> <pre><code>git svn clone http://path/to/repo/Root/Project1 --trunk=trunk --tags=tags Project1 </code></pre> <p>That is, almost the same as the second command that you use, but without the -b part. <code>git svn</code> won't try to look for branches if it is not requested to.</p> <p>After that, you could try editing <code>.git/config</code> as manojlds suggests.</p> <p><strong>EDIT</strong>: ok, I run further tests. I recreated an svn repository with your folder structure. I tried to use <code>git svn</code> on it and everything went smoothly. I'm using git 1.7.1.</p> <p>I then looked for the string "couldn't find revmaps" in <a href="http://www.google.com/codesearch" rel="nofollow">Google Code Search</a>, and found this:</p> <pre><code>sub lookup_svn_merge { ... my $gs = Git::SVN-&gt;find_by_url($url.$source, $url, $path); if ( !$gs ) { warn "Couldn't find revmap for $url$source\n"; return; } ... </code></pre> <p>I'm certainly not going to read the entire code for <code>git svn</code>, but what I surmise from this is that Git found a merge point in trunk, and the merge comes from a path that Git doesn't know anything about and that for some reason it can't reach.</p> <p>I tried to reproduce this case but all went successfully again. Possible solutions:</p> <ul> <li>upgrade your Git version if it's not the latest</li> <li>figure out if there's indeed a merge from SpecificBranchName1 in trunk, and if so, only use the revisions after that one to initialize your Git repository</li> </ul> <p>I hope this helps...</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload