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.
>
>
There's another option, which is to skip the "add" phase, and let
"svn cp" *replace* "svn co". Aren't mostly orthogonal file-system
analog operations nice?
I suggested this a few days ago, but my suggestion was met with
no reponse.
--ben
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 22 18:57:01 2002