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

Re: checkout

From: Duncan Murdoch <murdoch_at_stats.uwo.ca>
Date: 2006-05-08 15:32:43 CEST

On 5/8/2006 9:20 AM, Hector Alvarez Pol wrote:
> Ryan Schmidt wrote:
>> That is correct. You have set them up to be two independent
>> repositories, so you must check them out independently. If you wanted
>> to be able to check out a common parent directory, then you would
>> need to set the two projects up as directories within a single
>> repository.
> Thanks for your answer, Ryan, but I think I did not explain clearly what
> my problem is. I do not want to check out a common parent; I separate
> both repositories because I need two projects well separated.
> The question is that the remote checkout using http does not allow to
> get the trunk directory alone. I must checkout all the repository. And
> this impacts the directory structure in the remote computers.
> As explained in the previous mail, I cannot create in a remote computer
> a directory structure like:
> simsDir/
> |-> mySim1/
> |-> mySim2/
> cause the checkout of the second project is forbidden (the directory
> simsDir "is already a working copy for a different URL").
> This is solved if I could checkout the trunk directory inside the
> respositories...

Sorry for coming in late, you may already have explained this, but why
not make simsDir a regular (non-versioned) directory, and check out
mySim1 and mySim2 into it?

> So, it is not possible to get simply the trunk directory inside a
> repository using the checkout with http ?

I think what you can't do is checkout two different things to the
identical location. I don't think the protocol (http, etc) is relevant.

Duncan Murdoch

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon May 8 15:35:18 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.