Re: Split a subversion repo into several git repos

From: Patrick Doyle <wpdster@gmail.com>
Date: Oct 11, 2007, 14:02 UTC
Message-ID: <e2a1d0aa0710110702o359d6cd9yaa213be6a43924e4@mail.gmail.com>
In-Reply-To: <27DDC599-C7A0-4660-B5C6-7DFCEB137C14@steelskies.com>

On 10/11/07, Jonathan del Strother <maillist@steelskies.com> wrote:

Show 16 quoted lines

> I have a slightly different layout to you -
>
> projectA/trunk
> projectA/branches
> projectA/tags
> projectB/trunk
> projectB/branches
> projectB/tags
> etc
>
> - but I've been creating separate git repos from that with (for
> example) :
>
> git-svn init -t tags -b branches -T trunk http://svn.host.com/projectA
> git-svn fetch
>

Just be aware that, if you follow this approach, the commit logs created by git-svn will be rewritten (relative to the original SVN logs) with the SVN repository revision and ID information. I believe you can disable this behavior by passing the --no-metadata option to "git-svn init", but I haven't tried this yet.

I also believe that this approach will leave your git repository in such as state as to recognize that there is a remote repository from which this repository was fetched. I have no idea what implications and long term repercussions (if any) this has. It just dawned on me as I was rereading the git-svn man page to look for the --no-metdata option and read that it will "Set the noMetadata option in the [svn-remote] config". Most of that is still Greek to me.

--wpd