kmradke_at_rockwellcollins.com writes:
> This is PRECISELY a reason why I want/need a --force flag!!!!!
Are you confusing svn and svnmucc? I have never objected to you
adding a force flag to svn.
> Create it if needed, overwrite it if it exists. The svn cp
> functionality is modelled around the unix cp command which would
> do the exact same thing in your scenario above...
>
> Adding support for this doesn't make any "broken" behavior any worse
> (the user said to overwrite) and it makes the "check and overwrite"
> operation atomic which is impossible from any wrapper script.
>
> Do you have a better proposal for "fixing" cp functionality?
>
> Complaints that it is broken in other ways do not help and should
> not be a valid reason to reject simple beneficial behavior additions...
You keep saying the same things, so you will get the same answer. I
don't like the idea of adding a force flag to svnmucc, I'd prefer an
overwrite action.
If you want to propose a force flag for svn, rather than svnmucc, then
do the usual things: read the old discussions, start a new discussion,
write a patch, etc. There is at least one proposed patch in the issue
tracker.
---------------------------------------------------------------------
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-07 18:37:57 CET