On 7/12/05, nick vajberg <nickvajberg@yahoo.dk> wrote:
> I really dislike the proposal of just showing a
> partial list. There's a few tools that does this, and
> they routinely confuse me.
>
> The proper solution IMO is to group the commands into
> logical categories; grep --help is a guiding example.
>
> There should even be a short description for each
> command, as with grep and a host of other commands.
>
> A long list is not problematic as long as it is easy
> on the eye.
>
> I also dislike aliases. They do nothing but making the
> help output harder to read and remembering the
> commands gets more difficult for newbies. Making a
> command a bit shorter to write is no argument; that
> can be done by wrapper scripts for those in need.
>
> Four aliases for 'delete' is, well, three to many.
>
> So for instance (the categories would need some, uhm,
> work):
>
> Getting stuff from the repo:
> checkout
> commit
> update
>
> Stuff that only affects the working copy:
> ...
>
> Locking:
> lock
> unlock
> ...
>
> Properties
> propdel
> propedit
> propget
> ...
>
>
Any categorization will leave something to be desired, but how's this:
Making Changes
add
commit
copy
delete
import
mkdir
move
Viewing and Applying Changes
diff
merge
resolved
status
Retrieving Changes
update
checkout
possibly merge here instead of above
Working Copy Management
cleanup
export
info
revert
switch
Examining the Repository
log
list
blame
cat
Managing Properties
propdel
propedit
propget
proplist
propset
Managing Locks
lock
unlock
Misc
help
Josh
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jul 12 16:24:40 2005