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

RE: argh

From: Mats Nilsson <mats.nilsson_at_xware.se>
Date: 2002-07-28 18:30:54 CEST

Under this scheme, how would these cases be handled

svn co http://host/repos/trunk/doc http://host/repos/branches/bugfix1/doc
work-on-docs
or
svn co http://host1/repos/trunk http://host2/repos/trunk stuff

or other conceivable mishaps.

There is nothing particular to gain by allowing multiple check-out targets.
They are not necessarily related to the same revision, so they could just as
easily be separated into different commands.

Mats

> Justin Erenkrantz <jerenkrantz@apache.org> writes:
>
> Can't we just make it "do the right thing"? How about this
[...]
> - case 3: multiple URLs
> $ svn co http://host1/repos1/module1 http://host2/repos2/module2
> checkout into ./module1/ and ./module2/
>
> - case 4: multiple URLs and explicit path
> $ svn co http://host1/repos1/module1 http://host2/repos2/module2 path
> checkout into ./path/module1/ and ./path/module2/
>
> --
> Philip Martin

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Jul 28 18:32:42 2002

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.