From: Glen Choo <chooglen@google.com>
To: Victoria Dye via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org
Cc: derrickstolee@github.com, gitster@pobox.com,
Victoria Dye <vdye@github.com>
Subject: Re: [PATCH v2 1/3] config: use gitdir to get worktree config
Date: Wed, 31 May 2023 13:54:12 -0700 [thread overview]
Message-ID: <kl6lttvsnrwr.fsf@chooglen-macbookpro.roam.corp.google.com> (raw)
In-Reply-To: <fb597cdfeb033478103c81143e1b16dec957e0a4.1685064781.git.gitgitgadget@gmail.com>
"Victoria Dye via GitGitGadget" <gitgitgadget@gmail.com> writes:
> Finally, add tests to 't3007-ls-files-recurse-submodules.sh' to verify the
> corrected config is loaded. Use 'ls-files' to test this because, unlike some
> other '--recurse-submodules' commands, 'ls-files' parses the config of the
> submodule in the same process as the superproject (via 'show_submodule()' ->
> 'repo_read_index()' -> 'prepare_repo_settings()'). As a result,
> 'the_repository' points to the config of the superproject but the
> commondir/gitdir in the config sequence will be that of the submodule,
> providing the exact scenario needed to verify this patch.
>
> The first test ('--recurse-submodules parses submodule repo config') checks
> that the submodule's *repo* config is read when running 'ls-files' on the
> superproject; this confirms already-working behavior, serving as a reference
> for how worktree config parsing should behave. The second test
> ('--recurse-submodules parses submodule worktree config') tests the same
> scenario as the previous but instead using the *worktree* config,
> demonstrating the corrected behavior. The 'test_config' helper is extended
> for this case so that it properly applies the '--worktree' option to the
> configure/unconfigure operations it performs.
Thanks! This version is really clear.
> diff --git a/t/test-lib-functions.sh b/t/test-lib-functions.sh
> index 6e19ebc922a..b3864e22e9a 100644
> --- a/t/test-lib-functions.sh
> +++ b/t/test-lib-functions.sh
> @@ -542,8 +542,17 @@ test_config () {
> config_dir=$1
> shift
> fi
> - test_when_finished "test_unconfig ${config_dir:+-C '$config_dir'} '$1'" &&
> - git ${config_dir:+-C "$config_dir"} config "$@"
> +
> + # If --worktree is provided, use it to configure/unconfigure
> + is_worktree=
> + if test "$1" = --worktree
> + then
> + is_worktree=1
> + shift
> + fi
> +
> + test_when_finished "test_unconfig ${config_dir:+-C '$config_dir'} ${is_worktree:+--worktree} '$1'" &&
> + git ${config_dir:+-C "$config_dir"} config ${is_worktree:+--worktree} "$@"
> }
>
> test_config_global () {
The test_config() change looks good to me. In the future, I think we
should extend this so that we can get rid of test_config_global() (which
is basically the same thing) and have only have one way of doing this.
next prev parent reply other threads:[~2023-05-31 20:54 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 23:17 [PATCH 0/2] Fix behavior of worktree config in submodules Victoria Dye via GitGitGadget
2023-05-23 23:17 ` [PATCH 1/2] config: use gitdir to get worktree config Victoria Dye via GitGitGadget
2023-05-25 1:05 ` Glen Choo
2023-05-25 20:05 ` Derrick Stolee
2023-05-23 23:17 ` [PATCH 2/2] repository: move 'repository_format_worktree_config' to repo scope Victoria Dye via GitGitGadget
2023-05-25 1:29 ` Glen Choo
2023-05-25 16:09 ` Glen Choo
2023-05-25 20:02 ` Victoria Dye
2023-05-25 20:13 ` Derrick Stolee
2023-05-24 10:25 ` [PATCH 0/2] Fix behavior of worktree config in submodules Junio C Hamano
2023-05-25 19:56 ` Glen Choo
2023-05-26 1:32 ` [PATCH v2 0/3] " Victoria Dye via GitGitGadget
2023-05-26 1:32 ` [PATCH v2 1/3] config: use gitdir to get worktree config Victoria Dye via GitGitGadget
2023-05-31 20:54 ` Glen Choo [this message]
2023-05-26 1:32 ` [PATCH v2 2/3] config: pass 'repo' directly to 'config_with_options()' Victoria Dye via GitGitGadget
2023-05-26 1:33 ` [PATCH v2 3/3] repository: move 'repository_format_worktree_config' to repo scope Victoria Dye via GitGitGadget
2023-05-31 22:17 ` Glen Choo
2023-06-01 4:43 ` Junio C Hamano
2023-06-12 21:37 ` Glen Choo
2023-06-07 22:29 ` Victoria Dye
2023-06-12 18:10 ` Glen Choo
2023-06-12 19:45 ` Victoria Dye
2023-06-12 20:23 ` Glen Choo
2023-06-12 23:04 ` [PATCH] setup: copy repository_format using helper Glen Choo
2023-06-13 0:03 ` Victoria Dye
2023-06-13 18:25 ` Glen Choo
2023-06-13 19:45 ` Junio C Hamano
2023-05-26 15:48 ` [PATCH v2 0/3] Fix behavior of worktree config in submodules Derrick Stolee
2023-06-13 22:09 ` Glen Choo
2023-06-13 22:17 ` Victoria Dye
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=kl6lttvsnrwr.fsf@chooglen-macbookpro.roam.corp.google.com \
--to=chooglen@google.com \
--cc=derrickstolee@github.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
--cc=vdye@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).