From: Junio C Hamano <gitster@pobox.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Stefano Lattarini <stefano.lattarini@gmail.com>,
Stefan Beller <stefanbeller@googlemail.com>,
git@vger.kernel.org
Subject: Re: [PATCH] tag: Use OPT_BOOL instead of OPT_BOOLEAN to allow one action multiple times
Date: Sun, 18 Aug 2013 02:27:11 -0700 [thread overview]
Message-ID: <xmqqioz3e4cw.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20130817203458.GB2904@elie.Belkin> (Jonathan Nieder's message of "Sat, 17 Aug 2013 13:34:58 -0700")
Jonathan Nieder <jrnieder@gmail.com> writes:
> Stefano Lattarini wrote:
>
>> Why not encourage the use of a standardized '--action' option instead?
>
> Because it's an unpleasant UI. :)
>
>> This can work with lesser compatibility headaches for both the commands
>> taking mode options and the commands taking mode words:
>>
>> "git submodule init" becomes "git submodule --action=init"
>> "git tag --delete TAG" becomes "git tag --action=delete TAGNAME"
>
> That looks like a bad change in both cases --- it involves more
> typing without much upside to go along with it. But
>
> "git submodule init" gains synonym "git submodule --init"
> "git tag --delete TAG" stays as "git tag --delete TAG"
>
> looks fine to me.
I agree 100% with the above that illustrates why --action=<name> is
a bad idea. As I already said, adding action-option like --init, if
doing so might help people, I am not opposed to it.
Thanks.
prev parent reply other threads:[~2013-08-18 9:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 18:00 [PATCH] tag: Use OPT_BOOL instead of OPT_BOOLEAN to allow one action multiple times Stefan Beller
2013-07-30 19:24 ` Junio C Hamano
2013-07-30 21:22 ` Stefan Beller
2013-07-30 22:22 ` Junio C Hamano
2013-07-30 21:28 ` Stefan Beller
2013-07-30 22:28 ` Junio C Hamano
2013-07-31 10:34 ` Stefan Beller
2013-07-31 23:10 ` Junio C Hamano
2013-08-17 15:01 ` Stefano Lattarini
2013-08-17 20:34 ` Jonathan Nieder
2013-08-18 9:27 ` Junio C Hamano [this message]
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=xmqqioz3e4cw.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=stefanbeller@googlemail.com \
--cc=stefano.lattarini@gmail.com \
/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).