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

Re: Checking out multiple repositories.

From: Karl Fogel <kfogel_at_galois.collab.net>
Date: 2001-03-15 16:34:53 CET

No comment on your proposed implementation Fitz, but +1 on the
proposed behavior.

(I'd just be painting bike sheds if I started to talk about cl client
implementation at the moment, as you have far more knowledge of that
code's state than I do now.)

-K

"B. W. Fitzpatrick" <fitz@red-bean.com> writes:
> I know that you *just* got checkout working, but here's a huge comment
> that I dropped into client/checkout-cmd.c. Feel free to ignore it
> until you're ready for it... it's just an FYI.
>
> -Fitz
>
> TODO Fixme: This only works for one repo checkout at a shot. In
> CVS, when we checkout one project and give it a destination
> directory, it dumps it in the directory. If you check out more
> than one, it dumps each project into its own directory *inside*
> the one that you specified with the -d flag. So, for example, we
> have project A:
>
> A/one_mississippi.txt
> A/two_mississippi.txt
> A/three_mississippi.txt
>
> And project B:
>
> B/cat
> B/dog
> B/pig
>
> If I do 'cvs -d :pserver:fitz@subversion.tigris.org:/cvs co -d foo A', I get the following:
>
> foo/one_mississippi.txt
> foo/two_mississippi.txt
> foo/three_mississippi.txt
>
> But if I do this 'cvs -d :pserver:fitz@subversion.tigris.org:/cvs
> co -d foo A B', I get the following:
>
> foo/A/one_mississippi.txt
> foo/A/two_mississippi.txt
> foo/A/three_mississippi.txt
> foo/B/cat
> foo/B/dog
> foo/B/pig
>
> Makes sense, right? Right. Note that we have no provision for this
> right now and we need to support it. My vote is that we stop
> iterating over opt_state->args here and just pass the args into
> svn_client_checkout and let it decide what to do based on
> (args->nelts == 1) or (args->nelts > 1). -Fitz
Received on Sat Oct 21 14:36:26 2006

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

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