From: Dmitry Potapov <dpotapov@gmail.com>
Date: Sun, 20 Sep 2009 18:54:15 GMT
Subject: Re: Usability question
Message-ID: <20090920185415.GA6988@dpotapov.dyndns.org>
In-Reply-To: <513ca40e0909191921k1b7b14b5j7cfd8734441397d9@mail.gmail.com>

On Sun, Sep 20, 2009 at 12:21:38PM +1000, Rob Barrett wrote:
> On Thu, Sep 17, 2009 at 8:41 PM, Matthieu Moy
> <Matthieu.Moy@grenoble-inp.fr> wrote:
> > Well, if you want to get rid of subcommands, why not get rid of
> > commands, too?
> >
> > git --commit
> > git --status
> > git --svn --rebase
> >
> 
> Well, granted, that's a sort of heavyweight consistency, but all we
> should need to do is to help reduce a _new_ user's confusion about
> when the word after a subcommand gets a '--' prefix and when it
> doesn't.
> 
> And do it in a way that's backwards compatible so it doesn't affect
> the usage patterns of seasoned users, existing scripts, crons etc.
> 
> Will patch and see how it looks..

It will be horrible broken... Do you realize that there is a bigger
difference between commands and options than just that commands are
written without a '--' prefix? Take a look at the following commands:

$ git -p log
$ git log -p

There are completely difference because in the former case the -p
option modifies 'git' behavior while in the later case 'git log'.

If you change commands to options, you are going to break everything.


Dmitry