[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Migration thoughts, VSS/SOS to SVN

From: Thomas Harold <tgh_at_tgharold.com>
Date: 2006-10-20 16:40:09 CEST

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

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Oct 20 16:41:53 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.