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

Re: checkout structure || subscribe

From: Ryan Schmidt <subversion-2006Q1_at_ryandesign.com>
Date: 2006-03-03 17:39:21 CET

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:
>> http://subversion.tigris.org/issues/show_bug.cgi?id=695
> 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?

> 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
> for each module in proj1(*). However, running any svn commands at the
> root tree does not descend into the subdirs. This is because the
> directories aren't listed in the toplevel dir's .svn/entries file. I
> added a hack to the pull target to add any versioned subdirs to the
> entries file. This seems to let me do tree wide diffs & commits and
> seems to work for multiple branches. 'svn up' is somewhat flaky so we
> just stick with the pull targets. The hack doesn't work if you pull
> 'subdir/subsubdir' instead of 'subdir' since the .svn dir doesn't
> exist
> for the intermediate directory when doing:
> svn co $REPO/trunk/$mod/include $mod/include

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.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Mar 3 17:42:08 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.