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

Re: Partial Checkout feature request.

From: Sven Brueggemann <SBrueggemann_at_gmx.net>
Date: 2006-09-26 22:37:58 CEST


Michael Marcin wrote:
> /
> branches/
> tags/
> trunk/
> A/
> B/
> C/
> Where A/ B/ and C/ are each fairly large (say 100MB+)
> 1/3 of the people at our company need only A/
> 1/3 of the people need only B/ and C/
> and the rest need either all of trunk/ or some combination of its
> children.
> So the next thing we tried was to have everyone checkout exactly
> what they needed with several checkouts into the same directory.
> i.e. they would checkout trunk/B/ and checkout trunk/C/ to c:/trunk.
> Then highlight all folders in c:/trunk to do updates and commits. This
> however means that if there is a change to trunk/B/ and trunk/C/ at
> the same time the revision number is incremented once for each folder
> they checkout This makes seeing what changed in updates and going back
> to old versions very difficult.

What about this:

Create a folder D in the repository. It can be empty - I use it to
store files common to A, B and C.

Check out D to your hard drive (c:\WC} and create the folders for the
projects you need (say: c:\WC\B and c:\WC\C). Check out trunk/B to
c:\WC\B and trunk/c to c:\WC\C.

You now have working copies inside a working copy (nested WCs).

You can use c:\WC\B and c:\WC\C like any "normal" working copy. In case
you need to commit a change that affects both B and C, you can multi-select
both WCs and commit them together in a single revision. Or do the same
by selecting "commit" on any WC and drag and drop the changes from the
other WC to the commit dialog.

Kind regards


To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Tue Sep 26 22:40:07 2006

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.