From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: Philippe Blain via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org,
Philippe Blain <levraiphilippeblain@gmail.com>
Subject: Re: [PATCH v3 0/4] completion: remove hardcoded config variable names
Date: Tue, 13 Feb 2024 09:09:04 -0800 [thread overview]
Message-ID: <xmqq8r3o8f67.fsf@gitster.g> (raw)
In-Reply-To: <Zcs34kGTqTbIana6@tanuki> (Patrick Steinhardt's message of "Tue, 13 Feb 2024 10:35:30 +0100")
Patrick Steinhardt <ps@pks.im> writes:
> On Sat, Feb 10, 2024 at 06:32:19PM +0000, Philippe Blain via GitGitGadget wrote:
>> Changes since v2:
>>
>> * Moved the addition of the tests to 2/4, and tweaked 3/4 and 4/4 so they
>> simply adjust the test names
>> * Added a test for user-defined submodule names, as suggested by Patrick
>> * Added more details in the commit message of 3/4 around the use of global
>> variables as caches
>> * Slightly improved commit message wording and fixed typos
>> * Added 'local' where suggested
>> * Dropped 4/5 which modified 'git help', since it's not needed (thanks
>> Patrick!)
>>
>> Changes since v1:
>>
>> * Corrected my email in PATCH 2/5 (sorry for the noise)
>>
>> v1: This series removes hardcoded config variable names in the
>> __git_complete_config_variable_name function, partly by adding a new mode to
>> 'git help'. It also adds completion for 'submodule.*' config variables,
>> which were previously missing.
>>
>> I think it makes sense to do that in the same series since it's closely
>> related, and splitting it would result in textual conflicts between both
>> series if one does not build on top of the other, but I'm open to other
>> suggestions.
>>
>> Thanks,
>>
>> Philippe.
>
> I ain't got anything else to add to this patch series. Thanks!
Thanks, both. Let's mark it for 'next' so that it can be one of the
topics to graduate first after the current cycle.
prev parent reply other threads:[~2024-02-13 17:09 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-28 20:02 [PATCH 0/5] completion: remove hardcoded config variable names Philippe Blain via GitGitGadget
2024-01-28 20:02 ` [PATCH 1/5] completion: add space after config variable names also in Bash 3 Philippe Blain via GitGitGadget
2024-01-28 20:02 ` [PATCH 2/5] completion: complete 'submodule.*' config variables Philippe Blain via GitGitGadget
2024-01-28 20:02 ` [PATCH 3/5] completion: add and use __git_compute_first_level_config_vars_for_section Philippe Blain via GitGitGadget
2024-01-28 20:02 ` [PATCH 4/5] builtin/help: add --config-all-for-completion Philippe Blain via GitGitGadget
2024-01-28 20:02 ` [PATCH 5/5] completion: add an use __git_compute_second_level_config_vars_for_section Philippe Blain via GitGitGadget
2024-01-29 13:27 ` [PATCH v2 0/5] completion: remove hardcoded config variable names Philippe Blain via GitGitGadget
2024-01-29 13:27 ` [PATCH v2 1/5] completion: add space after config variable names also in Bash 3 Philippe Blain via GitGitGadget
2024-01-29 13:27 ` [PATCH v2 2/5] completion: complete 'submodule.*' config variables Philippe Blain via GitGitGadget
2024-02-08 7:42 ` Patrick Steinhardt
2024-02-10 15:39 ` Philippe Blain
2024-01-29 13:27 ` [PATCH v2 3/5] completion: add and use __git_compute_first_level_config_vars_for_section Philippe Blain via GitGitGadget
2024-02-08 7:42 ` Patrick Steinhardt
2024-02-10 16:06 ` Philippe Blain
2024-02-10 17:15 ` Junio C Hamano
2024-02-10 17:27 ` Philippe Blain
2024-02-14 0:24 ` Junio C Hamano
2024-01-29 13:28 ` [PATCH v2 4/5] builtin/help: add --config-all-for-completion Philippe Blain via GitGitGadget
2024-02-08 7:42 ` Patrick Steinhardt
2024-02-10 16:13 ` Philippe Blain
2024-01-29 13:28 ` [PATCH v2 5/5] completion: add an use __git_compute_second_level_config_vars_for_section Philippe Blain via GitGitGadget
2024-02-08 7:42 ` Patrick Steinhardt
2024-02-10 16:19 ` Philippe Blain
2024-02-07 22:08 ` [PATCH v2 0/5] completion: remove hardcoded config variable names Junio C Hamano
2024-02-08 7:42 ` Patrick Steinhardt
2024-02-10 18:32 ` [PATCH v3 0/4] " Philippe Blain via GitGitGadget
2024-02-10 18:32 ` [PATCH v3 1/4] completion: add space after config variable names also in Bash 3 Philippe Blain via GitGitGadget
2024-02-10 18:32 ` [PATCH v3 2/4] completion: complete 'submodule.*' config variables Philippe Blain via GitGitGadget
2024-02-10 18:32 ` [PATCH v3 3/4] completion: add and use __git_compute_first_level_config_vars_for_section Philippe Blain via GitGitGadget
2024-02-10 18:32 ` [PATCH v3 4/4] completion: add and use __git_compute_second_level_config_vars_for_section Philippe Blain via GitGitGadget
2024-02-13 9:35 ` [PATCH v3 0/4] completion: remove hardcoded config variable names Patrick Steinhardt
2024-02-13 17:09 ` Junio C Hamano [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=xmqq8r3o8f67.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=levraiphilippeblain@gmail.com \
--cc=ps@pks.im \
/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).