chongyc <chongyc27@xxxxxxxxx> wrote: > Hi > > I found that 'git svn fetch' failed in cloning the hudson svn reposotory. > > I want to git-clone the svn repository > > svn repository URL : https://svn.dev.java.net/svn/hudson/ > username : guest > password : > > > So I run followings to git-clone > > [root@localhost hudson]# git --version > git version 1.6.0.6 > [root@localhost hudson]# git svn init -T trunk -t tags -b branches > https://svn.dev.java.net/svn/hudson/ > [root@localhost hudson]# git svn fetch > Found possible branch point: > https://svn.dev.java.net/svn/hudson/tags/hudson-1_230 => > https://svn.dev.java.net/svn/hudson/branches/buildnav-1636, 10490 > Initializing parent: buildnav-1636@10490 > Found possible branch point: > https://svn.dev.java.net/svn/hudson/trunk/hudson/main => > https://svn.dev.java.net/svn/hudson/tags/hudson-1_230, 10450 > Initializing parent: buildnav-1636@10450 > Found branch parent: (buildnav-1636@10490) a1c395e5db063ca1ffbbe008e309c5 > 11d56219e0 > Following parent with do_switch > remoting/pom.xml was not found in commit > a1c395e5db063ca1ffbbe008e309c511d56219e0 (r10447) > [root@localhost hudson]# > > What shall I do to git-clone it ? > > Please help me Hi, sorry for the late reply, I've been very distracted. Looking at the hudson repository, the layout is non-standard and very complex, with subdirectories being branched and tagged all over. The standard globbing that git-svn uses for most repositories does won't work. You'll have to map things manually: [svn-remote "svn"] url = https://svn.dev.java.net/svn/hudson fetch = trunk/hudson:refs/remotes/trunk fetch = branches/tom:refs/remotes/tom ... Alternately, you could just clone the root and have all the branches all over the place in one tree (your eventually working copy will be huge). git svn clone https://svn.dev.java.net/svn/hudson Basically this is the equivalent of: svn co https://svn.dev.java.net/svn/hudson Except you'll have the full history. -- Eric Wong -- 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
