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

RE: Checkout trunk revisions of projects in a multi project repo?

From: John Niven <jniven_at_bravurasolutions.com>
Date: Mon, 6 Oct 2008 08:20:21 +1100

> -----Original Message-----
> From: Ryan Schmidt [mailto:subversion-2008c_at_ryandesign.com]
> Sent: Saturday, 4 October 2008 10:36
> To: cj91
> Cc: users_at_subversion.tigris.org
> Subject: Re: Checkout trunk revisions of projects in a multi
> project repo?
>
> On Oct 3, 2008, at 3:06 PM, cj91 wrote:
>
> > ...snip...
> >
> > We have Hundreds of projects in our repository in nested folders.
> > Is there a
> > way I can checkout the trunk versions of all the projects
> in the repo?
> > I'm not interested in the tagged or branched versions, just
> the trunk.
>
> You're supposed to issue a separate "svn checkout" command
> for each trunk that you would like to work on.
>
> svn checkout $REPO/Proj1/trunk
> svn checkout $REPO/Folder/Proj4/trunk
>
> And so on. Surely you don't need to work on all several
> hundred projects simultaneously? Check them out as you need them.

Or, if you feel you really must check them out in one big working copy, SVN 1.5 allows sparse checkouts - you'd checkout root specifying "--depth=immediates" and then update the trunks, specifying "--depth=infinity"

If it were me I'd want separate working copies, though - easier to keep different projects in different working copies.

Cheers
John

>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
> For additional commands, e-mail: users-help_at_subversion.tigris.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-10-05 23:20:50 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.