Pretty much. Starting with the synchronized repository (at revision x)
on my machine (and once all activity on SF has ceased), I will:
0. delete (svn remove) the trunk on SF repository (leaving it at
revision x + 1)
1. checkout the code (revision x) from my local copy of the repository
2. run the scripts
3. commit all the changes to the local copy of the repository
4. use svadmin dump to create the import data file(s)
5. use svnadmin load to import the data into a specific directory
on the Apache SVN repo
This supposes that I, or someone else, has access to the Apache SVN disk.
Rob
On 29/09/10 19:50, Dan Haywood wrote:
On 29/09/2010 19:39, Robert Matthews wrote:
I have a mirror that I will/can do an svn export from (once I've run
all the conversion scripts that I am preparing).
Can you confirm the steps you're intending to take, then? I'm
guessing it's something like:
1. take an svn dump from the SF.net website
2. perform a load into your local SVN repo
3. run the conversion steps on your local SVN repo
4. perform an svn dump from your local SVN repo
5. upload (via svnadmin) into the Isis repo
Do I have that right?
Dan
