Re: [PATCH v6 04/10] submodule: introduce extensions.submodulePathConfig

From: Josh Steadmon <steadmon@google.com>
Date: Dec 16, 2025, 23:22 UTC
Message-ID: <y7hfbq37mh2a6rnwvycul2e3fhxl7bljkdlukdpl3obgg57u3p@vgdsj2wo5nab>
In-Reply-To: <20251213080817.347922-5-adrian.ratiu@collabora.com>

On 2025.12.13 10:08, Adrian Ratiu wrote:

Show 13 quoted lines

> The idea of this extension is to abstract away the submodule gitdir
> path implementation: everyone is expected to use the config and not
> worry about how the path is computed internally, either in git or
> other implementations.
> 
> With this extension enabled, the submodule.<name>.gitdir repo config
> becomes the single source of truth for all submodule gitdir paths.
> 
> The submodule.<name>.gitdir config is added automatically for all new
> submodules when this extension is enabled.
> 
> Git will throw an error if the extension is enabled and a config is
> missing, advising users how to migrate. Migration is manual for now.

This part doesn't seem accurate in my testing. When cloning a project with `--recurse-submodules` and with the extension enabled globally, the resulting .git/config does not include gitdir configs for any of the cloned submodules, yet no error occurs.