Ryan Schmidt wrote:
> On Mar 3, 2006, at 17:23, Chris Seawood wrote:
>>> $ mkdir foo
>>> $ cd foo
>>> $ svn co -N $REPO/foo
>>> $ cd foo
>>> $ svn up -N tags branches
>>> $ svn up trunk branches/branchN
>>> Be aware that the -N option is broken in some ways:
>> How does that let you 'keep root control of the tree'? By root control,
>> I'm assuming that svn commands issued at the toplevel directory are
>> propagated to the subdirs so that you can do working copy wide svn
>> actions like diff & commit.
> Doesn't my way allow you to do that?
I initially thought it didn't but it turns out that I made a typo. That
method works for pulling from a single tree using the svn repo tree
hierarchy. However, it doesn't seem to work for creating a working copy
that contains dirs from multiple branches/tags. How would you create a
working copy that looks like:
wc/mod1 <-- trunk/mod1
wc/mod2 <-- branches/branch1/mod2
wc/mod3 <-- tags/tag2/mod3
that svn will see as a single working copy?
>> We ran into a similar problem here. We just migrated our CVS repo to
>> SVN 1.3.0 on Monday. We have several toplevel directories that pulled
>> for any particular project. Under CVS, we'd do:
>> cvs co mod1 mod2 mod3/include
>> for svn, we have do to:
>> svn co -N $REPO/trunk .
>> make -f top.mk pull_proj1
>> where, the makefile will run
>> svn co $REPO/trunk/$mod
> You're making many separate working copies, which Subversion will treat
> as separate entities. My way makes a single working copy (with some
> parts missing, as you wanted) so you should be able to do atomic
> operations across the whole of it.
That goes back to the question I asked in the previous email. Is there
a way to pull multiple "toplevel" dirs without using multiple commands?
Subversion seems to (wrongly) assume that a working copy will consist of
a directory structure that can be obtained by pulling a single
directory. Using the 'svn up -N' method works around the issue for
directories that live as direct subdir of the toplevel dir but I don't
immediately see how it can be extended to any branch/tag directory (or
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Fri Mar 3 18:22:33 2006