Hi Antonio,
On Thu, Apr 12, 2018 at 3:20 PM, Antonio Ospite <ao2@xxxxxx> wrote:
> When multiple repositories with detached work-trees take turns using the
> same directory as their work-tree, and more than one of them want to use
> submodules, there will be conflicts about the '.gitmodules' file.
unlike other files which would not conflict?
There might be file names such as LICENSE, Readme.md etc,
which are common enough that they would produce conflicts as well?
I find this argument on its own rather weak. ("Just delete everything in
the working dir before using it with another repository"). I might be
missing a crucial bit here?
> git hardcodes this path so it's not possible to override its location on
> a per-repository basis to allow such repositories to coexists
> peacefully.
>
> Make the path of the "gitmodules file" customizable exposing
> a 'core.submodulesFile' configuration setting.
>
> The default value will still be '.gitmodules' when 'core.submodulesFile'
> is not set.
ok.
> --- a/cache.h
> +++ b/cache.h
> @@ -1774,6 +1774,7 @@ extern void prepare_pager_args(struct child_process *, const char *pager);
> extern const char *editor_program;
> extern const char *askpass_program;
> extern const char *excludes_file;
> +extern const char *submodules_file;
Could you place this variable in repository.h in struct repository?
(Some developers currently try to move any global state to that place,
as that makes working with e.g. nested submodules easier in-process
and you would not need to spawn processes for submodules)
Once migrated to the repository struct mentioned above, you'd access
it via the_repository->submodules_file for the main repository.
> diff --git a/git-submodule.sh b/git-submodule.sh
> index 24914963c..610fd0dc5 100755
> --- a/git-submodule.sh
> +++ b/git-submodule.sh
> @@ -71,7 +71,9 @@ get_submodule_config () {
> value=$(git config submodule."$name"."$option")
> if test -z "$value"
> then
> - value=$(git config -f .gitmodules submodule."$name"."$option")
> + gitmodules_file=$(git config core.submodulesfile)
> + : ${gitmodules_file:=.gitmodules}
> + value=$(git config -f "$gitmodules_file" submodule."$name"."$option")
I wonder if it would be cheaper to write a special config lookup now, e.g.
in builtin/submodule--helper.c we could have a "config-from-gitmodules"
subcommand that is looking up the modules file and then running the config
on that file.
I am surprised how little access of the .gitmodules is left in git-submodule.sh
(which is partially ported to the builtin/submodule--helper.c)
> diff --git a/submodule-config.c b/submodule-config.c
> index 3f2075764..8a3396ade 100644
> --- a/submodule-config.c
> +++ b/submodule-config.c
> @@ -468,7 +468,7 @@ static int gitmodule_oid_from_commit(const struct object_id *treeish_name,
> return 1;
> }
>
> - strbuf_addf(rev, "%s:.gitmodules", oid_to_hex(treeish_name));
> + strbuf_addf(rev, "%s:%s", oid_to_hex(treeish_name), submodules_file);
> if (get_oid(rev->buf, gitmodules_oid) >= 0)
> ret = 1;
>
> @@ -583,7 +583,7 @@ void repo_read_gitmodules(struct repository *repo)
> if (repo_read_index(repo) < 0)
> return;
>
> - gitmodules = repo_worktree_path(repo, GITMODULES_FILE);
> + gitmodules = repo_worktree_path(repo, submodules_file);
>
> if (!is_gitmodules_unmerged(repo->index))
> git_config_from_file(gitmodules_cb, gitmodules, repo);
> diff --git a/submodule.c b/submodule.c
> index 9a50168b2..2afbdb644 100644
> --- a/submodule.c
> +++ b/submodule.c
> @@ -36,13 +36,13 @@ static struct oid_array ref_tips_after_fetch;
> */
> int is_gitmodules_unmerged(const struct index_state *istate)
> {
> - int pos = index_name_pos(istate, GITMODULES_FILE, strlen(GITMODULES_FILE));
> + int pos = index_name_pos(istate, submodules_file, strlen(submodules_file));
Ah, regarding the coverletter: This clearly assumes the modules
file is in the tree. So at least here we would make an exception
for files outside the tree to either not check for un-merged-ness or
disallow that case entirely.
There are quite a few functions in submodule.c which access the new global. :/
So moving them to the_repository should be fine, but eventually (not
in this series)
all these functions would would want to take a repository argument as well
such that they work on more than the_repository.
Thanks,
Stefan
