Re: thoughts about a checkout --force option?

Gary Wilson Jr wrote:
> Julian Foad wrote:
>> I wouldn't make "--force"
>>overwrite existing WCs unless and until someone demonstrated a good use
>>case for doing so.
>
> Yes, I think the main issues here are what the --force flag should force OR
> should more than one flag be introduced.
>
> Here are some options:

There's no point in suggesting user interfaces for forcibly overwriting WCs
unless and until we want that behaviour. Design the functionality of a feature
first, and the user interface afterwards.

Anyway, the "--force" option name is a vague catch-all. If more that one
option is to be used to control what behaviours are being forced, then the
options should be named according to what they do (e.g.
--overwrite-existing-working-copies), not given more vague names like
"--force-all", "--force-lots", "--force-some", etc.

- Julian

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue May 24 23:07:47 2005