All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Garrit Franke <garrit@slashdev.space>,
	git@vger.kernel.org, Taylor Blau <ttaylorr@github.com>
Subject: Re: [PATCH v2] cli: add -v and -h shorthands
Date: Fri, 01 Apr 2022 09:02:39 -0700	[thread overview]
Message-ID: <xmqqtubcyeow.fsf@gitster.g> (raw)
In-Reply-To: <220401.86y20pnofb.gmgdl@evledraar.gmail.com> ("Ævar Arnfjörð Bjarmason"'s message of "Fri, 01 Apr 2022 11:23:39 +0200")

Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:

>> Do you mean you want to use "-V" for version, instead of the "-v"
>> used in the patch, so that "-v" can be left for "--verbose"?
>>
>> I am not sure consistency with whom we are aiming for anymore with
>> that mixed to the proposal X-<.
>
> Maybe you've been convinced to accept -v and -h (I don't care much
> either way, honestly), but if not I wonder if this alternate approach
> would make everyone in this thread happy (or at least mostly so):

I don't care too much about being similar to stuff made by other
people, compared to how much I care about internal consistency ;-)

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.


  reply	other threads:[~2022-04-01 16:28 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 [this message]
2022-04-04  7:18               ` Garrit Franke
2022-04-04 16:19                 ` Junio C Hamano
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=xmqqtubcyeow.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.