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

Re: Is this a bug?

From: Garrett Rooney <rooneg_at_electricjellyfish.net>
Date: 2002-07-21 16:25:01 CEST

On Sun, Jul 21, 2002 at 04:15:08PM +0200, Marcus Comstedt wrote:
>
> Marcus Comstedt <marcus@mc.pp.se> writes:
>
> > So in this case the error message is correct. '.' isn't a working
> > copy directory. Question is, if that's a problem, shouldn't the
> > command fail _before_ writing all the files to foobar? And if it
> > isn't a problem (foobar seems to become a proper wc dir), then there
> > shouldn't be an angry message about it.
>
> Hm, when I think about it a little more, I can see two correct ways of
> handling svn cp to a non-wc:
>
> 1) bomb out early
>
> or
>
> 2) do exactly what svn export does
>
> Rationale for 2) is this: svn cp should get the contents of the files
> from URL, but transfer version control to that of the destination,
> right? So in the case where the destination is not version
> controlled, you should just get the files without version control.

i'd say it should bomb out early. if you want to export, you should
use export. overloading the meaning of copy just leads to a confusing
interface.

-garrett

-- 
garrett rooney                    Remember, any design flaw you're 
rooneg@electricjellyfish.net      sufficiently snide about becomes  
http://electricjellyfish.net/     a feature.       -- Dan Sugalski
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Jul 21 16:25:29 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.