Re: [PATCH] Ignore the fact that a file is versioned when -F is passed to a subcommand different then 'commit'

On Sun, 2002-01-27 at 00:08, Lars Kellogg-Stedman wrote:
> In a situation where your syntax boils down to:
>
> command [ common_options ] subcommand [ subcommand_options ]

Well, we specifically didn't want to get into the situation CVS has
where an option can mean one thing before the subcommand thing and a
different thing after. For a given subcommand, all options mean the
same thing regardless of which position you put them in.

To keep things simple, we use the same option spec for all subcommands.
(If option specs differed noticeably between subcommands, we could get
into awkward situations trying to determine the subcommand name; is "svn
-a -b foo bar" the foo command with the -a and -b options, or the bar
command with the -a and "-b foo" options? Conceivably it could be
both.) Sometimes that might lead to issues like the confusing error
message, but any other satisfactory way would be rather complicated.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:37:00 2006