So, I tried to clone the repository with this command:
git svn clone -T trunk -t tags/6.x -b branches/6.x <svn_url>/<proj_name>
After it completed, I went it to the .git/config file and added a few
more branches/tags from other locations:
[svn-remote "svn"]
url = https://<svn_url>/<proj_name>
fetch = <proj_name>/trunk:refs/remotes/trunk
branches = <proj_name>/branches/{6.x,5.x}/*:refs/remotes/*
branches = <proj_name>/branches/*:refs/remotes/*
tags = <proj_name>/tags/{3.7.x,4.x,5.x,6.x,old-releases}/*:refs/remotes/tags/*
Is my syntax even correct? Can I have more than one "branches"
property? How do I tell git-svn to re-sync with the latest branch/tag
locations?
Thanks!
On Mon, Apr 19, 2010 at 5:18 PM, Bradley Wagner
<bradley.wagner@xxxxxxxxxxxxxx> wrote:
> I'm trying to port an SVN project to Git. We have gone through
> multiple layouts for our SVN repository. It started off with just a
> mainline branch in the root folder. Then we went to the standard
> layout (branches, trunk, tags).
>
> The problem is that when I do a "git svn clone --stdlayout" of the
> repository, it's not picking up any of the revisions from when the
> trunk previously resided in the root directory.
> Is there any way to specify that the trunk had multiple paths the way
> you can specify multiple branch folders with -b flag? What would be
> the best course of action for reporting an SVN repo who's layout had
> changed during its history?
>
> Thanks,
> Bradley
>
--
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