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

Re: Emphasizing commonly-used commands in 'svn help' output.

From: Joshua Varner <jlvarner_at_gmail.com>
Date: 2005-07-12 16:23:47 CEST

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

Viewing and Applying Changes

Retrieving Changes
  possibly merge here instead of above

Working Copy Management

Examining the Repository

Managing Properties

Managing Locks



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

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.