cmd line stuff (was: CVS update: ...)

On Tue, Oct 17, 2000 at 12:05:49AM -0000, kfogel@tigris.org wrote:
>...
> +A start on global options:
> +
> + -r repository Use REPOSITORY.

Wouldn't this be an argument to the checkout command? Or are we planning to
allow some of the commands when a working copy does not exist? e.g. why
specify the repository for an "update" ?

> + -f Suppress reading of .svnrc.
> + -h -H --help [command] Like CVS: get general or cmd-specific help.
> + --help-options (Also like the CVS help scheme.)
> + --help-commands (Same.)
> + --dry-run Like cvs -n
> + -q Quiet. (No need for two levels of this?)
> + -v --version Print program name, version, and url.

-v for verbose? Will we have a verbose option? [and version would be -V]

> +And the commands will look a lot like CVS's, though there are some
> +newcomers:
> +
> + checkout | co
> + update | up
> + commit | ci
> + add | ad | new
> + rename | mv
> + delete | del | rm
> + copy | cp
> + branch /* implemented via copy, though may want to be its own command */
> + tag /* implemented via copy, though may want to be its own command */
> + status | stat
> + diff | di | dif
> + rdiff

what the heck is rdiff?

> + annotate | ann
> + import | im | imp

export?

> + history | hi | his
> + log | lo

how are history and log different?

> + propset | pset
> + propget | pget

Will we have a "login" command? A URL can specify a user/password, but I'm
sure many people will want prompts to keep the pwd off the cmd line.

Speaking of: I think we can skip that whole "munge the pwd before storing in
.cvspass" is bogus. Just store it in clear text and chmod the file properly.
The cmd line should abort operation if the perms on that file are incorrect
("your .svnrc file has incorrect permissions, please set to 0600" or
whatever).

Along a similar line, there are going to be different ways to authenticate
with the server. Sometimes, we may not even have a password :-) Other times,
we need to somehow figure out where a client-side certificate is stored.

> +Some command-specific options are unique to that command, but others
> +are common to several commands, for example:
> +
> + -v version Like "cvs cmd -r REV"

urk. Is it possible to avoid duplicate letters between the global and local
options? Dunno how much people confuse them, but it might be a nice start.

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/