[bikeshed] --allow-overwrite ? (was: svn commit: rev 6327 - in trunk/subversion: clients/cmdline include libsvn_client)

On Mon, Jun 23, 2003 at 09:22:35PM -0500, sussman@tigris.org wrote:
> Author: sussman
> Date: Mon Jun 23 21:22:23 2003
> New Revision: 6327
>
> Modified:
> trunk/subversion/clients/cmdline/export-cmd.c
> trunk/subversion/clients/cmdline/main.c
> trunk/subversion/include/svn_client.h
> trunk/subversion/libsvn_client/client.h
> trunk/subversion/libsvn_client/export.c
> Log:
> Issue #1296: add --force option for svn export, so an exported
> directory can be overwritten by a subsequent export. Patch from

Should we maybe nip the "force _what_?" question in the bud and just stop
using --force? Maybe rename this as --allow-overwrite ?

[ note that the same switch could be used for people who want to check out
  over the top of unversioned files :-) ]

I find that using something like --allow-overwrite will be much more
intuitive than --force. Especially given our command help. Take a look at
the help for force: "force operation to run". Hunh? With the non-force
style, we can have tuned help. And I think the tuned help will be more
beneficial than the cost of the corresponding increase in the number of
option flags. (I note that the help for 'svn export' doesn't even mention
the semantics of the --force switch)

Here are the other '--force' users:

  delete: force the removal of unversioned items
  merge: dunno what force does here
  move: dunno

We have "--force-log" which is nice and customized, although I'm sure we
could bikeshed on the naming there, too :-). (but, thankfully, the hard work
of separating it out has been done)

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org