Re: git-svn and migration
- From
Steven Walter <stevenrwalter@gmail.com>
- Date
- Dec 19, 2007, 17:54 UTC
- Message-ID
- <20071219175447.GB15898@dervierte>
- In-Reply-To
- <320075ff0712190850r35263bcfv1d8f84e699208e15@mail.gmail.com>
On Wed, Dec 19, 2007 at 04:50:30PM +0000, Nigel Magnay wrote:
Show 6 quoted lines
> Has anyone got any tips as I'm sure it's a path trodden before? I've > seen examples of keeping a read-only svn, but that's not really what > I'm after. I'm considering whether to have a central git repo > regularly pull from svn so that it's up to date, and having us > possibly push to svn (or git if it's not merged to trunk) as an > interim step..
Using a central git repo that is kept uptodate with svn is the approach I've used. git-svn isn't especially keen on this mode of operation, however. After every fetch, you have to reset refs/remotes/trunk to origin/master, which it turn puts .git/svn out of date (you can blow it away and run "git svn fetch" to regenerate it).
I wrote a script that automates most of this stuff (including doing incremental additions to git-svn's revdb/revmap). If there's interest, I can see about cleaning it up for general consumption.
-- -Steven Walter <stevenrwalter@gmail.com> Freedom is the freedom to say that 2 + 2 = 4 B2F1 0ECC E605 7321 E818 7A65 FC81 9777 DC28 9E8F