Kevin Radke <kmradke_at_gmail.com> writes:
> Philip Martin wrote:
>> kmradke_at_rockwellcollins.com writes:
>
>>> 2) Modify svn cp to allow a --force behavior
>>
>> svn cp with URLs already has some unpredictable behaviour, I'm not
>> sure whether force would make it better or worse :)
>
> This confuses me as well too. You specify a source rev and path
> and a target path. What is unpredictable about that? (other
> than possibly passing HEAD as rev which could change)
Consider:
svn cp URL/foo URL/bar
if this command works a new revision is created but the user won't
know what that revison contains. The only way to determine which of
URL/bar or URL/bar/foo got created is to examine the repository after
the commit. Without exclusive access to the repository it is
impossible to predict the outcome of the copy. That's a terrible
interface for anyone building tools on top of Subversion.
>
>>> 3) Create a new tool based on svnmucc, add --force behavior
>>> and contribute to contrib?
>>
>> That would be silly.
>
> But you are essentially telling me to re-implement (and possibly not
> distribute) custom wrapper scripts. I believe that is silly.
>
>> I remain unconvinced about your patch; perhaps somebody else will
>> venture an opinion?
>
> I don't mind not using the patch as is. I'm looking for guidance
> on what is acceptable behavior so I can create a new patch.
Although I still struggle to see why anybody would want it, I have
already expressed a preference for adding an overwrite action rather
than adding a force flag. I'd like the action to make directory
overwrites work over all RA layers and I'd like to see a check to
catch the current directory overwrite bug (since I don't think the
server is going to get fixed in the near future).
---------------------------------------------------------------------
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 13:57:46 CET