On 4/19/07, David Glasser <glasser@mit.edu> wrote:
> On 4/19/07, C. Michael Pilato <cmpilato@collab.net> wrote:
> > If you wish to create a sparse copy, you can still use sparse-directories to
> > assist in this, but it takes just a little more effort. (You need to do a
> > full checkout of the pieces you want to keep, with a depth-zero checkout of
> > any "limbs" you wish to "prune"; schedule those to-be-pruned limbs for
> > deletion, then do a wc-to-repos copy.) Or, ask Karl points out, you can use
> > MUCC, issuing the copy + all the pruning deletions you need in a single
> > transaction.
>
> Does the current implementation give an interface to "schedule those
> to-be-pruned limbs for deletion"?
Ah yes, if there was a single operation to accomplish that, then the
sparse copy becomes a simple two-step operation: mark all to-be-pruned
limbs for deletion, then issue the wc->url copy. I don't see that in
the notes on sparse support, however.
Kylo
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Apr 19 20:05:08 2007