"Orgad Shaneh via GitGitGadget" <gitgitgadget@xxxxxxxxx> writes:
> The member is set to true only when pathspec was given, and is
> used when a submodule that matched the pathspec is found
> uninitialized to give diagnostic message. "submodule update"
> without pathspec is supposed to iterate over all submodules
> (i.e. without pathspec limitation) and update only the
> initialized submodules, and finding uninitialized submodules
> during the iteration is a totally expected and normal thing that
> should not be warned.
> ...
> builtin/submodule--helper.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/builtin/submodule--helper.c b/builtin/submodule--helper.c
> index 2c87ef9364f..1a8e5d06214 100644
> --- a/builtin/submodule--helper.c
> +++ b/builtin/submodule--helper.c
> @@ -2026,7 +2026,6 @@ struct update_data {
> .references = STRING_LIST_INIT_DUP, \
> .single_branch = -1, \
> .max_jobs = 1, \
> - .warn_if_uninitialized = 1, \
> }
Is this a fix we can protect from future breakge by adding a test or
tweaking an existing test? It is kind of surprising if we did not
have any test that runs "git submodule update" in a superproject
with initialized and uninitialized submodule(s) and make sure only
the initialized ones are updated. It may be the matter of examining
the warning output that is currently ignored in such a test, if
there is one.
Thanks.
