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

Re: "svn ls" too complex?

From: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2002-08-01 19:51:08 CEST

On Thu, 2002-08-01 at 12:36, Karl Fogel wrote:
> I'm not exactly sure what problem you're proposing solving here...

I'm not proposing anything. Nick Bastin said we should have
subcommand-specific options, and I was arguing against him.

Just to recap, the choices are:

  * Options have different meanings before and after the subcommand.
    (This is what CVS does.)

  * Options have the same meaning for all subcommands, except for
    disallowed combinations. (This is what we do.)

  * Options have different meanings for different subcommands, but have
    the same meaning whether they appear before or after the subcommand.
    Can create parsing ambiguities, so this is a non-starter.

  * Options have different meanings for different subcommands, and can
    only appear after the subcommand name. This is a viable scheme, but
    it has its disadvantages, and there's no compelling reason to switch
    to it.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 1 19:58:06 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.