Philip Martin <philip_at_codematters.co.uk> wrote on 11/06/2008 12:37:13 PM:
> "Kevin Radke" <kmradke_at_gmail.com> writes:
>
> > svnmucc would allow an user to use "CP REV SRC DST" when both SRC and
> > DST URLs were directories. It would (silently) "replace" DST with
> > SRC. When used with specific file names it would return an error that
> > "DST already exists".
>
> When I try the current trunk build the copy fails for both files and
> directories. The svnmucc test suite is rather small and doesn't test
> this behaviour so it may have been different in the past, but I'd be
> surprised if it has changed.
I only tested my original 1.5.1 install and then built against trunk,
but I'm not sure anything changed to affect this...
> > This simple patch makes it consistently "replace" the target no matter
> > if it is a file or a directory. I believe this functionality is much
> > nicer, since the user does not need to "check and delete if exists"
> > before doing the copy operation.
>
> I prefer the current error; I think it's better than replacing the
> history of something that exists.
It is painful (for us) to not have an option to overwrite contents.
Silently overwriting is a little dangerous, but no history is
overwritten. You can always go back to the old revision number...
Since it already overwrote for directories for me, I didn't think
making it behave the same for files was much of a jump...
Personally, I started adding a --force option to the regular svn cp
command, until I realized svnmucc did *almost* what I needed it to.
I've found users from other CM systems are really annoyed by not
being able to "easily" re-label/re-tag something with the same name.
While you can script around this by "check if it exists, delete
if it exists, copy", that is much more complicated for the
nontechnical user.
Kevin R.
Received on 2008-11-06 20:03:49 CET