To upload the history of an existing Subversion repository, use the svnsync tool that ships with Subversion 1.4. Run svnsync help to see the help for this tool.
Note that your Code Spaces Subversion repository must be at revision 0 to perforn a sync operation, so create a new repository if you need to.
Here’s a sample transcript that demonstrates how you can import the history from an existing repository (located at file:///c:/path/to/localrepos) to your repository on Code Spaces:
Windows:
C:\> svnsync init --username YOURUSERNAME https://svn.codespaces.com/YOURACCOUNT/YOURREPOSITORY file:///c:/path/to/localrepos
Copied properties for revision 0.
C:\> svnsync sync --username YOURUSERNAME https://svn.codespaces.com/YOURACCOUNT/YOURREPOSITORY
Committed revision 1.
Copied properties for revision 1.
Committed revision 2.
Copied properties for revision 2.
[...]
OSX or Linux:
$ svnsync init --username YOURUSERNAME https://svn.codespaces.com/YOURACCOUNT/YOURREPOSITORY file:///path/to/localrepos
Copied properties for revision 0.
$ svnsync sync --username YOURUSERNAME https://svn.codespaces.com/YOURACCOUNT/YOURREPOSITORY
Committed revision 1.
Copied properties for revision 1.
Committed revision 2.
Copied properties for revision 2.
[...]
When prompted for your password, use your Code Spaces password.
Running svnsync on a large repository will take a significant amount of time. If you are disconnected during the process, you may see the error message “svnsync: Couldn’t get lock on destination repos after 10 attempts”. If this happens, you can remove the lock yourself, see the “Locks” section of svnsync.txt.


