On Thu, Aug 27, 2009 at 10:32 AM, Daniele Segato<daniele.bilug@xxxxxxxxx> wrote: > Hi, this is my first message in the list: this may be a newbie > question and my English may not be very good. to prove my sentence: the subject should have been "git-svn-Cloning repository with _complex_ nesting" :-) I received help on IRC (#git) and managed to setup the svn-remote in an acceptable way > I've an SVN repository structured like this: > > http://<url>/path/to/repo > | > HEAD > |----- root > | > BRANCHES > |----- V1.0 > | |----- root > | > |----- V1.1 > | |----- root > | > |----- V1.2 > | |----- root > | > |----- DEV > | |----- FEATURE1 > | | |----- root > | | > | |----- FEATURE2 > | | |----- root > | | > | |----- FEATURE3 > | |----- root > | > |----- BUILDS > |----- BUILD1 > | |----- root > | > |----- BUILD2 > | |----- root > | > |----- BUILD3 > |----- root this is my setting: git init git svn init svn://svn.mydomain.com/path/to/repo -T HEAD -b BRANCHES -t TAGS vim .git/config # edited the svn-remote config as follow: [svn-remote "svn"] url = svn://svn.mydomain.com fetch = path/to/repo/HEAD/root:refs/remotes/svn/trunk branches = path/to/repo/BRANCHES/*/root:refs/remotes/svn/* tags = path/to/repo/TAGS/*/root:refs/remotes/svn/tags/* git svn fetch it seems to work as expected: only those branches that has a "root" folder got downloaded and fetched. I still couldn't retrieve the DEV/FEATUREx branches in that way. On IRC they told me I can add another line for branches: branches = path/to/repo/BRANCHES/*/*/root:refs/remotes/svnbis/* but I haven't been successful on this. They told me that I can add multiple branches lines only on newer versions of git. Probably that's the reason for that. I have git version 1.5.6.5. It is not a big deal: I can live without those branches even if I'll like to have them too. I have another problem now on that SVN repo but I'll open another topic about that because it is not related. Regards, Daniele -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html