From: Karl Hasselström Date: Thu, 11 Oct 2007 14:50:19 GMT Subject: Re: Split a subversion repo into several git repos Message-ID: <20071011145019.GA5315@diana.vm.bytemark.co.uk> In-Reply-To: On 2007-10-11 10:02:21 -0400, Patrick Doyle wrote: > 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. Just to clarify: this is true for all git-svn use, and has nothing to do with this particular case. > 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. Apart from the metadata appended to the commit messages (which you can turn off with --no-metadata), all the extra data saved by git-svn is purely local. Meaning that you can always get rid of it by cloning the repository, if you can't think of a cleverer way to do it. -- Karl Hasselström, kha@treskal.com www.treskal.com/kalle