Re: [PATCH] make svnmucc consistently overwrite copy targets

kmradke_at_rockwellcollins.com writes:

> Philip Martin <philip_at_codematters.co.uk> wrote on 11/06/2008 12:37:13 PM:
>>
>> 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...

To go back to the old revision you have to notice that the copy became
a replace, and since it would happened silently it's easy to miss. I
have no direct experince in this particular case, but in general I
find it "painful" when things misbehave silently. I'm more inclined
to add a check to prevent the directory/dav replace then to enable
file replacement.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-11-06 20:32:15 CET