From: Junio C Hamano <gitster@pobox.com>
To: "René Scharfe" <l.s.r@web.de>
Cc: "Jeff King" <peff@peff.net>,
"Git Mailing List" <git@vger.kernel.org>,
"Martin Ågren" <martin.agren@gmail.com>,
"Thomas Rikl" <trikl@online.de>,
"Thomas Gummerer" <t.gummerer@gmail.com>,
"Jonathan Nieder" <jrnieder@gmail.com>
Subject: Re: [Alt. PATCH] ls-remote: deprecate -h as short for --heads
Date: Tue, 24 Oct 2017 09:52:58 +0900 [thread overview]
Message-ID: <xmqqbmkxbc45.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <7c53071a-5154-1246-d2f1-1064e3f923d4@web.de> (=?utf-8?Q?=22R?= =?utf-8?Q?en=C3=A9?= Scharfe"'s message of "Mon, 23 Oct 2017 17:05:23 +0200")
René Scharfe <l.s.r@web.de> writes:
> Am 21.10.2017 um 14:18 schrieb Junio C Hamano:
>> René Scharfe <l.s.r@web.de> writes:
>>
>>> FWIW, I use "-?" for that everywhere. I have yet to find a command or
>>> environment where it does something dangerous.
>>
>> Yeah, it would have made the world a better place if we made that
>> choice back in 2008. If we start a transition to make it so right
>> now, we might be able to make the world a better place by 2022,
>> perhaps. I am not sure if the pain during the transition is worth
>> it, though.
>
> "-?" works fine with builtins already -- they complain that the option
> is unknown and then show the short help text.
Ah, I misunderstood what you meant, then. I thought you were
advocating to move the built-in short-help support to know about and
explicitly react to "-?", and somehow forgot that it "works" more or
less already.
The fact that "-?" already works for most things is good, but the
transition pain still remains, as what's costly is to transition
people's expectation (i.e. "'-?' and not '-h' is the way to get
short help from any subcommand"), not the implementation to fill the
gaps for those that do not yet support '-?', I am afraid.
next prev parent reply other threads:[~2017-10-24 0:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-15 10:02 Bug: git ls-remote -h / --head results differ in output Thomas Rikl
2017-10-15 11:08 ` Martin Ågren
2017-10-15 13:26 ` René Scharfe
2017-10-17 15:39 ` [PATCH 1/2] git: add NO_INTERNAL_HELP flag for builtins René Scharfe
2017-10-17 17:39 ` Jonathan Nieder
2017-10-17 15:39 ` [PATCH 2/2] ls-remote: use PARSE_OPT_NO_INTERNAL_HELP René Scharfe
2017-10-17 17:42 ` Jonathan Nieder
2017-10-17 17:42 ` Martin Ågren
2017-10-17 15:39 ` [Alt. PATCH] ls-remote: deprecate -h as short for --heads René Scharfe
2017-10-17 17:40 ` Martin Ågren
2017-10-17 17:43 ` Jonathan Nieder
2017-10-17 23:22 ` Junio C Hamano
2017-10-19 18:26 ` René Scharfe
2017-10-19 20:32 ` Jeff King
2017-10-20 1:04 ` Junio C Hamano
2017-10-20 3:05 ` Jeff King
2017-10-20 5:35 ` Junio C Hamano
2017-10-21 7:16 ` Jeff King
2017-10-21 10:14 ` René Scharfe
2017-10-21 12:18 ` Junio C Hamano
2017-10-23 15:05 ` René Scharfe
2017-10-24 0:52 ` Junio C Hamano [this message]
2017-10-24 18:26 ` René Scharfe
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqbmkxbc45.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=l.s.r@web.de \
--cc=martin.agren@gmail.com \
--cc=peff@peff.net \
--cc=t.gummerer@gmail.com \
--cc=trikl@online.de \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.