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

client README stuff

From: Bruce Korb <bkorb_at_cruzio.com>
Date: 2000-10-31 06:12:21 CET

  Parsing Command-Line Arguments

  The CVS custom of switching on a subcommand seems to work out pretty
  well, so we'll do the same thing. But many people have mentioned that
  having separate global versus command-local option namespaces is

< confusing. So Subversion has one option namespace, and all options
< come after the subcommand.

> confusing.  So each subversion subcommand will have one option name
> space and all options come after the subcommand.
   svn  [<subcommand>]  [<option> ...]  [<argument> ...]
Notes: the subcommand is marked as optional because there are a few
cases where Subversion can do something meaningful without the
< command, for example, "svn --help".
> command.  Specifically, `svn --help' is supported, along with the
> short option equivalents of `svn -h', `svn -?' and `svn -H'.
  [[Do we really want all these aliases supported directly?
  One of these, fine.  The others could just be declared invalid
  and cause an abbreviated help message. - b]]
  -v --version VER     Like "cvs -r" Subversion does not have revisions,
                       we have versions. Multiple version #s are
                       separated by a `,'
This spec conflicts with the usual and customary usage of the
`--version' option.  I am _strongly_ in favor of minimizing such
differences and do not see a compelling reason for a variation here.
How about `--file-version' or `--repository-version' or
`--object-version'?  *ANY*thing except `--version', please.
Received on Sat Oct 21 14:36:13 2006

This is an archived mail posted to the Subversion Dev mailing list.