From: Junio C Hamano <gitster@pobox.com>
To: Jacob Keller <jacob.keller@gmail.com>
Cc: "Git mailing list" <git@vger.kernel.org>,
"SZEDER Gábor" <szeder.dev@gmail.com>,
"Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>,
"Jonathan Nieder" <jrnieder@gmail.com>
Subject: Re: What's cooking in git.git (Jun 2020, #02; Wed, 10)
Date: Wed, 10 Jun 2020 18:56:47 -0700 [thread overview]
Message-ID: <xmqqbllqcqlc.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <CA+P7+xpMp1Zu6UAoN=uebZ-KOjuhSAJTTnCyHMPxZENweMvCjQ@mail.gmail.com> (Jacob Keller's message of "Wed, 10 Jun 2020 17:16:16 -0700")
Jacob Keller <jacob.keller@gmail.com> writes:
> On Wed, Jun 10, 2020 at 4:40 PM Junio C Hamano <gitster@pobox.com> wrote:
>> * jk/complete-git-switch (2020-05-28) 16 commits
>> - completion: improve handling of --orphan option of switch/checkout
>> - completion: improve handling of -c/-C and -b/-B in switch/checkout
>> - completion: improve handling of --track in switch/checkout
>> - completion: improve handling of --detach in checkout
>> - completion: improve completion for git switch with no options
>> - completion: improve handling of DWIM mode for switch/checkout
>> - completion: perform DWIM logic directly in __git_complete_refs
>> - completion: extract function __git_dwim_remote_heads
>> - completion: replace overloaded track term for __git_complete_refs
>> - completion: add tests showing subpar switch/checkout --orphan logic
>> - completion: add tests showing subpar -c/C argument completion
>> - completion: add tests showing subpar -c/-C startpoint completion
>> - completion: add tests showing subpar switch/checkout --track logic
>> - completion: add tests showing subar checkout --detach logic
>> - completion: add tests showing subpar DWIM logic for switch/checkout
>> - completion: add test showing subpar git switch completion
>>
>> The command line completion (in contrib/) learned to complete
>> options that the "git switch" command takes.
>>
>> Is this ready?
>>
>
> I don't think anyone besides you has reviewed this, and no one has
> commented on the most recent round. I believe this is ready, and in my
> day-to-day experience while using this has greatly improved. However,
> given that no one else has reviewed it...
>
> Based on a quick blame it looks like some of the most recent
> contributors who might be good persons to review this include SZEDER,
> Nguyễn Thái Ngọc Duy, and Jonathan Nieder.
Alright. Unless I hear otherwise by a few days, I'll plan to merge
this topic to 'next'.
Thanks.
next prev parent reply other threads:[~2020-06-11 1:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 23:36 What's cooking in git.git (Jun 2020, #02; Wed, 10) Junio C Hamano
2020-06-10 23:57 ` brian m. carlson
2020-06-11 0:27 ` Junio C Hamano
2020-06-11 0:16 ` Jacob Keller
2020-06-11 1:56 ` Junio C Hamano [this message]
2020-06-17 8:07 ` Shourya Shukla
2020-06-17 8:14 ` Kaartic Sivaraam
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=xmqqbllqcqlc.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jacob.keller@gmail.com \
--cc=jrnieder@gmail.com \
--cc=pclouds@gmail.com \
--cc=szeder.dev@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.
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).