> Greg Hudson wrote:
>
>> Operative rev defaults to peg rev:
>> cat
>> export
>> info
>> ls
>> propget
>> proplist
>>
>> Operative rev defaults to HEAD:
>> blame
>> co (bug: @pegrev not trimmed off default wc pathname)
>> diff (second operative rev defaults to HEAD)
I would say those three are wrong, and that the operative rev should default to
the peg rev. I would be a bit hesitant about fixing them, though, because of
backward compatibility. We really, really need a bit of documentation for the
command-line client that sets out the general principles of its interface.
Just a few paragraphs at the beginning of the command reference in the book.
If we had that already, we could say for certain that these are bugs and we
could fix them without worrying about compatibility with a mode of operation
which has been released into the wild but happened by accident. Grrr.
Any volunteers to
* write those introductory paragraphs;
* fix that "@pegrev not trimmed" bug that Greg mentioned above;
* decide whether we should fix the op.rev. default of these three commands
?
>> Does not appear to support peg revs even though it could:
>> cp
>> log
>> switch
These ought to grow support for peg revs, for consistency.
[1] Here's a start.
From "svn help":
> Most subcommands take file and/or directory arguments, recursing
> on the directories. If no arguments are supplied to such a
> command, it recurses on the current directory (inclusive) by default.
From subversion/clients/cmdline/main.c:
> * In most of the help text "PATH" is used where a working copy path is
> * required, "URL" where a repository URL is required and "TARGET" when
> * either a path or an url can be used. Hmm, should this be part of the
> * help text?
- Julian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Nov 28 19:32:01 2005