[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

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

From: <cmpilato_at_collab.net>
Date: 2003-06-25 08:58:35 CEST

Ben Collins-Sussman <sussman@collab.net> writes:

> Greg Stein <gstein@lyra.org> writes:
> > > 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 ?
> +1. I think --force is used way too generically all over the place.
> > Here are the other '--force' users:
> >
> > delete: force the removal of unversioned items
> > merge: dunno what force does here
> > move: dunno
> Do others agree? I know I've heard other people grumbling about the
> overloading of "--force", don't remember who. Anyone wanna file an
> issue to rename these switches?

As long as there's only one meaning per subcommand, I'm fine with
--force. My recent complaints (and changes) were because of an
overlap in meanings.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jun 25 08:58:34 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.