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

Re: setprop vs. propset

From: Karl Fogel <kfogel_at_red-bean.com>
Date: Wed, 27 Aug 2008 15:09:15 -0400

Neels Hofmeyr <neels_at_elego.de> writes:
> The second one could be paraphrased: "To make it easier to type a
> subcommand". IMHO, `setprop' sits much better in my brain, to the degree
> that it involuntarily turns `propset' around do `setprop'.
> Once that's there, I'd expect `sp' to work as well.

But alias space doesn't come free, remember. Someday later, we might
want 'sp' for "show patch". Or whatever, I don't know -- the point is,
if we expand too many commands into large equivalence classes, those
classes will inevitably start to interfere with future commands.

I think that introducing "setprop" is not actually a good idea. The
vast majority of people are not even using the command-line client at
all; of those who are, very few have complained about this. I
understand that for them it's a real issue -- I am not trying to deny
this. But I'm not sure the cost of fixing it is worth the gain. Having
"setprop" does imply having "sp"; having "sp"; likewise with "getprop"
and "gp". We shouldn't close off alias space for such small gains.


To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-08-27 21:29:37 CEST

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.