From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Garrit Franke <garrit@slashdev.space>
Subject: gf/shorthand-version-and-help (was: What's cooking in git.git (Apr 2022, #01; Mon, 4))
Date: Wed, 06 Apr 2022 10:56:02 +0200 [thread overview]
Message-ID: <220406.86o81eegf6.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <xmqqilropo3z.fsf@gitster.g>
On Mon, Apr 04 2022, Junio C Hamano wrote:
> * gf/shorthand-version-and-help (2022-03-31) 1 commit
> - cli: add -v and -h shorthands
>
> "git -v" and "git -h" are now understood as "git --version" and
> "git --help".
>
> Will merge to 'next'?
> source: <20220331212709.36036-1-garrit@slashdev.space>
I've reviewed it and it looks good to me, and per my reply in the thread
I don't think we need to worry about squatting on a potential top-level
--verbose short flag.
prev parent reply other threads:[~2022-04-06 12:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 20:53 What's cooking in git.git (Apr 2022, #01; Mon, 4) Junio C Hamano
2022-04-04 23:20 ` ns/batch-fsync (Mon Apr 4, 2022) Neeraj Singh
2022-04-04 23:31 ` rsbecker
2022-04-05 4:35 ` Neeraj Singh
2022-04-05 12:35 ` rsbecker
2022-04-06 15:02 ` Junio C Hamano
2022-04-06 8:56 ` Ævar Arnfjörð Bjarmason [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=220406.86o81eegf6.gmgdl@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=garrit@slashdev.space \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 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 NNTP newsgroup(s).