At 12:25 PM 02/09/2005 -0400, Marc wrote:
>Ben Collins-Sussman wrote:
>>
>> * implements 'svn checkout --takeover' rather than 'svn takeover'
>>
>> --> We have a great resistance to adding new subcommands.
>> The main use-case for this feature is to avoid having to
>> to do a full checkout immediately after an import.
>
>I thought from my read of the threads after this patch that the
>consensus among the developers was that --force was the appropriate flag
>for this feature?
>
>The documentation for --force in the general svn switches section of the
>book certainly seems applicable here, IMO:
>> --force
>>
>> Forces a particular command or operation to run. There are some
>> operations that Subversion will prevent you from doing in normal
>> usage, but you can pass the force switch to tell Subversion “I know
>> what I'm doing as well as the possible repercussions of doing it, so
>> let me at 'emE This switch is the programmatic equivalent of doing
>> your own electrical work with the power on—if you don't know what
>> you're doing, you're likely to get a nasty shock.
I disagree with this interpretation, personally. To me, '--force' in the
context of 'checkout' sounds like "even if files by the same name are in
the WC, overwrite them with the copy being checked out". I personally think
the operation is different enough from a "checkout", whose purpose is to
create a WC rather than assume one, to warrant a new command, but if it
really cannot be a command unto itself, I think the flag should be
'--takeover'.
Obviously, this is a trivial thing to change back and forth, so I'll just
proceed with the patch and tweak it to whichever one is agreed upon before
submitting it.
Jonathan Gilbert
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Sep 2 19:54:16 2005