From: Dmitry Potapov <dpotapov@gmail.com>
To: Rob Barrett <barrettboy@gmail.com>
Cc: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>, git@vger.kernel.org
Subject: Re: Usability question
Date: Sun, 20 Sep 2009 22:54:15 +0400 [thread overview]
Message-ID: <20090920185415.GA6988@dpotapov.dyndns.org> (raw)
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
next prev parent reply other threads:[~2009-09-20 18:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-17 10:01 Usability question Rob Barrett
2009-09-17 10:41 ` Matthieu Moy
2009-09-17 12:13 ` SZEDER Gábor
2009-09-17 13:09 ` Matthieu Moy
2009-09-17 13:25 ` Daniele Segato
2009-09-20 2:21 ` Rob Barrett
2009-09-20 18:54 ` Dmitry Potapov [this message]
2009-09-17 11:20 ` Owen Taylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090920185415.GA6988@dpotapov.dyndns.org \
--to=dpotapov@gmail.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=barrettboy@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).