Re: Migration thoughts, VSS/SOS to SVN
Great feedback. Between this and the other thread regarding testimonials, I may actually be finally able to get the rest of our product development groups to move off the VSS+SOS configuration. I hate hearing the screaming coming from that side of the building every other month.
I do have a question on one of your points:
> - The command-line client and the TortoiseSVN client make it difficult to grab an arbitrary folder that is 2-4 levels deep in the hierarchy without wasting time pulling down other projects that we don't need on our local working copies. We're waiting for RapidSVN to release their 1.4 version to see if that does a better job for that particular usage scenario.
> The alternative would've been to create a few hundred repositories (one per job#) which is a management nightmare and even worse from the user's perspective. Plus, we're operating under the constraint that some of the tools that we use require working copy folder locations to be identical across each user's machine. (This happens on the Mac side of the business as well. There are many tools that use absolute paths and cause issues when files change location between working copies.)
In our group, we can use TortoiseSVN's repository browser when we do a checkout to drill all the way down to a specific folder and select that for checkout. When we do that, we get only that folder and the sub-objects (folders and files) of that folder. So if I want to only pull the code for a branch/project that one of my developers is working on I drill in and select only his/her specific working area, not every branch. And these might be anywhere from 2-10 levels deep, depending on the scope of the branch. So I am a bit curious where your issue above is coming from.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Fri Oct 20 16:15:36 2006
This is an archived mail posted to the Subversion Users