Good idea, but unfortunately, it does not work. $ LC_ALL=C git svn clone --trunk=trunk/ --branches=branches/ --branches=/ --tags=tags/ --prefix=origin/ file:///var/lib/svn/myrepository Initialized empty Git repository in /home/bjoern/myrepository/.git/ ref: 'refs/remotes/origin/' ends with a trailing slash, this is not permitted by git nor Subversion
Am Donnerstag, 21. Januar 2016 12:45:49 UTC+1 schrieb Konstantin Khomoutov: > > On Thu, 21 Jan 2016 03:23:55 -0800 (PST) > Björn Keil <schatt...@googlemail.com <javascript:>> wrote: > > > I am having a little trouble with importing an Subversion repository > > with a somewhat unusual layout: > > > > - *trunk/ *- The normal development trunk > > - *branches/ *- Perfectly normal branches folder. The subfolders > > (not branches itself) contain basically a different version of trunk. > > - *tags/ - *Hardly ever used, but it is there. > > - *live/ - *this *is *a branch, unlike the directory "branches/", > > which only *contains *branches. > > > > I've tried > > git svn clone \ > > --trunk=trunk/ \ > > --branches=branches/ --branches=live \ > > --tags=tags \ > > --prefix=origin/ \ > > file:///var/lib/svn/myrepository > > > > and while it seems to process revisions that concern changes in live/ > > I don't see how to access it. Is there a way to treat the "live/" > > directory in SVN as though it was "branches/live/" upon Git import > > without actually changing the Subversion repository? Or maybe do it > > after the initial "clone", but then I need the "rebase" to still work. > > Just out of curiousity, will it do what you want with > > git svn clone \ > ... \ > --branches=branches/ --branches=/ \ > ... > > ? > -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
