[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: Greg Stein <gstein_at_lyra.org>
Date: 2003-06-24 22:22:57 CEST

On Tue, Jun 24, 2003 at 04:07:13PM -0400, Greg Hudson wrote:
> On Tue, 2003-06-24 at 14:03, Ben Collins-Sussman wrote:
> > 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.
> I'm ambivalent on the main idea.
> But if we build this bikeshed, I think we should paint it
> --force-overwrite rather than --allow-overwrite, because I think that
> color would be more intuitive to most users.

Hmm. So if a file isn't there to be overwritten, does it put one in so it
can force an overwrite?

/me ducks


Maybe a different way to phrase it, is that the option should probably be in
passive voice (--allow-overwrite) rather than active (--force-overwrite).
You let the export do something, rather than make it do something. *shrug*

Mostly, I just want to see --force disappear. The resulting bikeshedded
names are less important to me.


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
Received on Tue Jun 24 22:18:28 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.