Re: [PATCH] Allow replace on repo-to-repo copy

On 1/25/07, Garrett Rooney <rooneg@electricjellyfish.net> wrote:
> On 1/25/07, Hyrum K. Wright <hyrum_wright@mail.utexas.edu> wrote:
>
> > I will agree that the svn commandline client lacks repository replace
> > functionality, but I don't think that the copy command is the correct
> > place to add it. At this point, I'm not sure where is ('svn replace'?)
>
> One thing that was suggested in the past was a 'svn copy --overwrite'
> option, which would indicate that if the target directory existed it
> would be overwritten instead of copied into. I believe there were
> some rather extensive discussions of this in the archives, but nobody
> moved past the discussion into actual coding.
>

I understand that the default semantics are to copy into the
destination if it exists. As I explained, my patch doesn't change the
default behavior of copy, it adds a switch called --replace which
changes the default behavior to replace the destination instead of
copy into it (if it exists). If the destination exists then adding
--replace changed nothing. In fact, specifying --replace for any copy
command other than a repo-to-repo copy where the destination exists
changes nothing in the default behavior.

I'll try to find the older discussions.

-- 
Justin Patrin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org