From: Stefan Beller <stefanbeller@gmail.com>
To: GIT Mailing-list <git@vger.kernel.org>
Subject: Unify subcommand structure; introduce double dashes for all subcommands?
Date: Wed, 23 Jul 2014 15:35:22 +0200 [thread overview]
Message-ID: <53CFBA1A.8040600@gmail.com> (raw)
In the user survey 2012 question 23 ("In your opinion, which areas in
Git need improvement?"),
the most crucial point identified was the user interface.
I wonder if there are any more recent surveys, showing if this has changed.
Now when we want to improve the user interface, we're likely talking
about the porcelain
commands only, as that's what most users perceive as the commandline
user interface.
A git command is generally setup as:
git <command> [<subcommand>] [<options>] ...
The subcommands vary wildly by the nature of the command. However all
subcommands
could at least follow one style. The commands bundle, notes, stash and
submodule
have subcommands without two leading dashes (i.e. git stash list) as
opposed to all
other commands (i.e. git tag --list).
So my proposal is to unify the structure of the subcommands to either
have always
leading dashes or never. This would need a longterm thinking of course
(e.g. introduce new options with(out) dashes, but support existing
commands until git 3.0
or such, then drop them.)
Was there a discussion about this topic already?
I'd like to read on these discussions, if any.
I could think about the following points being interesting
* user interface (what is more appealing to a user?)
* ease of transition (Is it really worth it? How long does it take to
pay off?)
* ease of implementation (Could we reuse the option parser already in
place for the double-dashed subcommands, i.e. have less LoC)
* error-proneness of the transition
Thanks,
Stefan
next reply other threads:[~2014-07-23 13:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 13:35 Stefan Beller [this message]
2014-07-23 17:52 ` Unify subcommand structure; introduce double dashes for all subcommands? Junio C Hamano
2014-08-10 15:26 ` Stefan Beller
2014-08-10 18:13 ` Junio C Hamano
2014-08-10 21:08 ` Stefan Beller
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=53CFBA1A.8040600@gmail.com \
--to=stefanbeller@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).