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

Re: svn prop* syntax weirdness

From: Karl Fogel <kfogel_at_newton.ch.collab.net>
Date: 2002-11-07 16:07:00 CET

David Summers <david@summersoft.fay.ar.us> writes:
> > | prop (p): Manipulate versioned properties on files
> > | usage: 1. prop --list [WC_TARGETS]
> > | 2. prop --get PROPNAME [WC_TARGETS]
> > | 3. prop --delete PROPNAME [WC_TARGETS]
> > | 4. prop --edit PROPNAME [WC_TARGETS]
> > | 1. prop --set PROPNAME [PROPVAL | -F VALFILE] [WC_TARGETS]
>
> I like this idea VERY well. It is essentialy subcommands to the prop
> command.

Could work, yah. Doesn't seem vastly better or worse than separate
prop commands, IMHO. Mmmm, except that it's not as conducive to
abbreviation -- 'plist', etc -- which would be a pity for experienced
users.

I don't think we should worry *too* much about minimizing the command
set so that the output of 'svn help' is short, because

   1. We're only accumulating commands over time anyway (i.e., that
      output is already not short),

   2. Beginners learning the tool don't learn it from that output
      anyway, it's more for experienced users needing a quickref,

   3. The eye automatically groups the "prop*" stuff together, so it
      takes up proportionally less mental space than it occupies in
      the help text.

So while neither way is an unambiguous win over the other, I would
somewhat prefer to retain the separate subcommands and just add a
--revprop or --revision-prop flag.

Anyway, I've put issue #943 into milestone 0.16, and referred to this
thread from it, since it would be good to get prop -r working soon.

-Karl

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Nov 7 16:40:13 2002

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.