Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to email@example.com.
On Wed, 08 Apr 2009 11:23:30 +0000, Tony Hoyle wrote: ... > A cvsnt client can't copy a subdirectory, and svn client can. The cvsnt > user has two choices (a) do it the old way, copy/add the files, or (b) > walk over to the nearest svn user, ask them to copy it, and do an update > on his own workstation. ..or do the svn command on its own machine. ... > So a hardcore cvsnt user would choose (a) every time. ...and get the flames when the next merge fails because of the mergeinfo that wasn't created because he carried over the files by hand. On the other hand 'svn copy' basically only exists to create tags and branches anyway. Who ever needs two directories that are mergeable to each other within a project tree? > Someone with a bit of flexibility would choose (b). They might even > choose to switch their sandbox to something else permanently - which > they can do without affecting their teammates or the project as a whole > (except the time taken to switch, which of course might by itself > preclude such an action). You don't need to switch hard. There is no problem with creating the svn sandbox and getting it to work before removing the cvsnt one. Andreas