> In article <9DB60651-A99D-423A-B453-98193513B7A1_at_ryandesign.com>,
> Ryan Schmidt <subversion-2009a_at_ryandesign.com> writes:
>> I suggest you ask Codeplex how they want you to import your existing
>> Subversion repository into their system.
> svnsync was the suggestion, which doesn't operate entirely within the
> bounds of what a pure client can do -- it requires a hook. Codeplex
> isn't a subversion guru outfit. I'm asking here because this is where
> the subversion gurus are located.
> Actually, my whole problem would be solved if svnadmin dump/load
> worked with URLs and not just paths.
> Why doesn't svnadmin dump/load work with URLs?
Because svndump works on repositories on the filesystem (e.g. the
administration) level. The result of an svn load is a repository, hardly
what you want when moving to TFS.
You actually need a TFS Guru since that is your target system. Codeplex
does not provide svn support, it allows you to use TotroiseSVN (instead
of the insanely unusable VS source control client) against TFS repositories.
I have to tell you, since you are moving from svn to TFS: welcome to a
world of pain.
I have rarely encountered a worst SCM experience then the one I have to
daily deal with TFS - to my knowledge only VSS was worse (and I've
worked with ClearCase, RCS, CVS, Perforce, svn, mercurial and git :) )
For the flame record, I am not a huge svn fan, but it beats working with
To your problem: Unless you find a ready made migration solution out
there (I haven't found one) you'll have to put your own together. This
http://migrationsynctoolkit.codeplex.com/ might help.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-04-05 09:55:41 CEST