From: Junio C Hamano <gitster@pobox.com>
To: Garrit Franke <garrit@slashdev.space>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
git@vger.kernel.org, "Taylor Blau" <ttaylorr@github.com>
Subject: Re: [PATCH v2] cli: add -v and -h shorthands
Date: Mon, 04 Apr 2022 09:19:51 -0700 [thread overview]
Message-ID: <xmqqbkxgstw8.fsf@gitster.g> (raw)
In-Reply-To: <f39ae520-a370-a1c5-7dcc-1b7bba4306bf@slashdev.space> (Garrit Franke's message of "Mon, 4 Apr 2022 09:18:17 +0200")
Garrit Franke <garrit@slashdev.space> writes:
> On 01.04.22 18:02, Junio C Hamano wrote:
>
>> I do not think one extra level of "unknown option", even with hint,
>> is worth the trouble. If we want to cater to those who expect "-h"
>> to be more special than random "-<some single letter>", we should go
>> all the way and make "-h" truly supported. If we do not, they can
>> read "git help git" just like those who wonder what "git -X" means.
>
> From what I gathered, we all agree that adding the "-h" shorthand is a
> good addition to the UI. Given that the "-v" option is understandably
> controversial, I could cut it from this patch.
>
> Thoughts?
I do not care too deeply, and it is the most time efficient to just
take the last patch as-is. Nobody would care they used "git -h" or
"git -v" only once and learned to use "git help" and "git version"
anyway ;-)
next prev parent reply other threads:[~2022-04-04 21:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 19:09 [PATCH v2] cli: add -v and -h shorthands Garrit Franke
2022-03-30 21:53 ` Junio C Hamano
2022-03-30 22:50 ` Garrit Franke
2022-03-31 0:07 ` Ævar Arnfjörð Bjarmason
2022-03-31 13:08 ` Garrit Franke
2022-03-31 20:07 ` Junio C Hamano
2022-04-01 9:23 ` Ævar Arnfjörð Bjarmason
2022-04-01 16:02 ` Junio C Hamano
2022-04-04 7:18 ` Garrit Franke
2022-04-04 16:19 ` Junio C Hamano [this message]
2022-03-31 21:27 ` [PATCH v3] " Garrit Franke
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=xmqqbkxgstw8.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--cc=garrit@slashdev.space \
--cc=git@vger.kernel.org \
--cc=ttaylorr@github.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.
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.