Thomas Harold wrote:
> Frank Gruman wrote:
>> 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.
> I have a lengthy post over at the TSVN lists, but I'll summarize here. It could be PEBKAC issue with me not selecting the right option:
> Gets checked out locally to
> Assuming that the user has C:\Ours\Jobs\A already created, they would right-click on the "A" folder, go to TSVN's repository browser. The Repo-Browser will open up at URL:
> Then we browse down to:
> At this point I have the following choices when I right-click on the folder in the Repository Browser:
> 1) Export... - Not what I want since I want a local working copy
> 2) Checkout... - Sounds like what I want, but the Checkout dialog comes up with a blank checkout directory text box. Which requires manual intervention by the user (which could result in non-standard folder paths in their local working copy).
> 3) Something else?
> Could you please explain a bit clearer how you're accomplishing that feat? It would eliminate a huge complaint that I'm going to get from my users.
If I create a local folder d:\test
My repository browser = projects/MMS/Release/MMS5.4_10.01/Setupdir
If I select the Checkout option from the right-click, I get the following output:
Completed: At revision: 6012
where 0007 and 0009 are subdirectories of the folder that I just selected in the repo-browser.
For what it's worth, I am using SVN version 1.4.0 as well as TortoiseSVN 1.4.0.
Perhaps the question back to you is this - is any part of the existing local folder structure above your example already a working copy? If so, then I could see where your issue comes from. But then I have to ask why all of that needed to be checked out to begin with.
Does each user have to keep a copy of every project they are working with in this same structure on their local pc? Or could they simply create a folder of c:\ours\jobs\ACWI01030_PipeDreams and then check out the repository folder of the same name into that?
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Fri Oct 20 17:54:43 2006