git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Rob Barrett <barrettboy@gmail.com>
To: git@vger.kernel.org
Subject: Usability question
Date: Thu, 17 Sep 2009 20:01:00 +1000	[thread overview]
Message-ID: <513ca40e0909170301s2b09184akb27acde76975c09b@mail.gmail.com> (raw)

When starting with git people almost always ask some variant of "how
do I know whether this option should be prefixed with dashes or not?"
i.e. git reset --hard vs. git stash save --patch, which coupled with
other path, sha and treeish args make things a bit more confusing.

Not sure if this has been discussed before? If it has point me at the
discussion and I'll go look at it -- no need to read further.

And people stop asking the question after they get used to git - but
that's not the same as being usable.

Out of 60+ commands, most take the form
git <subcommand> [--option]
and a few take the form
git <subcommand> subsubcommand [--option]

(a quick scan gives: bisect,bundle,reflog,remote,stash)

My questions:
1. What is the distinction that makes the 10% special enough to get
non-prefixed options?
2. Is it worthwhile? Wouldn't it be better if to shoot for more
consistency / less complexity?

Rob

             reply	other threads:[~2009-09-17 10:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-17 10:01 Rob Barrett [this message]
2009-09-17 10:41 ` Usability question 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
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=513ca40e0909170301s2b09184akb27acde76975c09b@mail.gmail.com \
    --to=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).