From: Felipe Contreras <felipe.contreras@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: RE: What's cooking in git.git (Dec 2020, #03; Fri, 18)
Date: Sat, 19 Dec 2020 08:10:09 -0600 [thread overview]
Message-ID: <5fde09c1ac7d_1def912083c@natae.notmuch> (raw)
In-Reply-To: <xmqq7dpeqrz4.fsf@gitster.c.googlers.com>
Junio C Hamano wrote:
> * fc/bash-completion-post-2.29 (2020-11-10) 26 commits
> - completion: bash: shuffle __gitcomp functions
> - completion: bash: cleanup __gitcomp* invocations
> - completion: bash: add __gitcomp_opts
> - completion: bash: improve __gitcomp description
> - completion: bash: rename _get_comp_words_by_ref()
> - completion: bash: trivial cleanup
> - completion: bash: cleanup _get_comp_words_by_ref()
> - completion: bash: refactor _get_comp_words_by_ref()
> - completion: bash: simplify _get_comp_words_by_ref()
> - test: completion: switch __gitcomp_nl prefix test
> - completion: bash: simplify config_variable_name
> - completion: bash: improve __gitcomp suffix code
> - completion: bash: change suffix check in __gitcomp
> - completion: bash: simplify __gitcomp
> - completion: bash: refactor __gitcomp
> - completion: bash: simplify equal suffix check
> - completion: bash: factor out check in __gitcomp
> - completion: bash: get rid of any non-append code
> - completion: bash: get rid of _append() functions
> - completion: bash: remove non-append functionality
> - test: completion: add run_func() helper
> - test: completion: fix currently typed words
> - completion: bash: do not modify COMP_WORDBREAKS
> - completion: bash: fix for suboptions with value
> - completion: bash: add correct suffix in variables
> - completion: bash: fix prefix detection in branch.*
>
> Needs review.
I think I already mentioned these should be dropped in favor of an
easier to digest series [1].
I just sent another try as a reminder [2].
Cheers.
[1] https://lore.kernel.org/git/20201119015209.1155170-1-felipe.contreras@gmail.com/
[2] https://lore.kernel.org/git/20201219140621.1961760-1-felipe.contreras@gmail.com/
--
Felipe Contreras
next prev parent reply other threads:[~2020-12-19 14:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-19 5:34 What's cooking in git.git (Dec 2020, #03; Fri, 18) Junio C Hamano
2020-12-19 6:44 ` Eric Sunshine
2020-12-19 17:13 ` Junio C Hamano
2020-12-19 14:10 ` Felipe Contreras [this message]
2020-12-19 17:09 ` Junio C Hamano
2020-12-20 2:19 ` Elijah Newren
2020-12-20 7:32 ` Junio C Hamano
2020-12-21 17:25 ` Elijah Newren
2020-12-21 17:50 ` Junio C Hamano
2020-12-21 12:40 ` Han-Wen Nienhuys
2020-12-21 18:01 ` Junio C Hamano
2020-12-21 19:55 ` [PATCH] SQUASH??? allow t0031 to run with any default branch name Junio C Hamano
2020-12-21 20:19 ` Felipe Contreras
2020-12-22 10:22 ` Han-Wen Nienhuys
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=5fde09c1ac7d_1def912083c@natae.notmuch \
--to=felipe.contreras@gmail.com \
--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).