From: William Hall <will@gnatter.net>
Date: Thu, 17 Jun 2010 10:33:43 GMT
Subject: Re: SVN migration
Message-ID: <4C19FA07.9010603@gnatter.net>
In-Reply-To: <7B0F34CE-9C9F-4FC3-AD96-8B1B8DD4359B@gmail.com>

Thanks Steven,

The noMetadata option will prevent me from doing anything other than a 
one-shot import, which is not what I want. I need to somehow devise a 
workflow that allows me bidirectional push/pull between an svn repo and 
a remote git repo.



Steven Michalske wrote:
> On Jun 16, 2010, at 4:02 PM, William Hall wrote:
> 
>> The issue is the dcommit operation from the bridge. The rebase part of this re-writes the commit messages to include the SVN commit-ids which is nice, but screws up the push/pulls between the bridge and the bare repo.
> 
> Look into svn.noMetadata configuration option.  It will prevent you from rebuilding the svn to git bridge if something seriously goes wrong, but it prevents the messages from changing.
> 
> svn-remote.<name>.noMetadata
> This gets rid of the git-svn-id: lines at the end of every commit.
> If you lose your .git/svn/git-svn/.rev_db file, git svn will not be able to rebuild it and you won't be able to fetch again, either. This is fine for one-shot imports.
> The git svn log command will not work on repositories using this, either. Using this conflicts with the useSvmProps option for (hopefully) obvious reasons