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

Re: Checkout question

From: John Peacock <john.peacock_at_havurah-software.org>
Date: Mon, 19 May 2008 07:25:54 -0400

David Aldrich wrote:
> Now suppose a user realises he need files from MyProject/B as well. Can he
> checkout B alongside A in the current working copy, or does he need to create
> a new working copy?


        $ svn co MyProject/A

produces a directory called A which is a working copy anchored in that portion
of the tree.

        $ svn co MyProject/B

produces a directory called B which is a working copy anchored in that portion
of the tree.

Those two working copies are completely independent, and in fact totally
ignorant of each other's presence. They are not the same working copy, even
though those folders are peers in the repository. Through some trickery, it may
be possible to join those two working copies together, but I don't feel
comfortable advocating the machinations involved because it is more than a
little hacky (and honestly, I'd have to try it myself to make sure I got it

There will be a feature in 1.5.0 called "relative externals" where you could
take some portion of B and embed it inside of A, without the distraction
associated with ordinary externals (like not being able to commit changes in a
single transaction to both the base URL and the external URL). I don't know if
this will help you or not.

For the present, the only good solution is to throw away the full A (and B)
checkouts and do this instead:

        $ svn co MyProject



1) it involves the variously broken "non-recursive" checkout option...

To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-05-19 13:25:38 CEST

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.