Re: [PATCH 02/15] submodule doc: write down what we want to achieve in this series

From: Junio C Hamano <gitster@pobox.com>
Date: Apr 26, 2016, 22:42 UTC
Message-ID: <xmqqd1pcc7r4.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <1461703833-10350-3-git-send-email-sbeller@google.com>

Stefan Beller <sbeller@google.com> writes:

> +When operating on submodules you can either give paths to specify the
> +desired submodules or give no paths at all to apply the command to the
> +default group of submodules.

So, "git submodule foo path1 path2" would act on path1 and path2 but would omit path3. If you have path1 and path3 but not path2 in the default group, and do not give any path, i.e. "git submodule foo", it would act on path1 and path3 but would omit path2.

OK so far.

> +By default all submodules are included in
> +the default group.

So if you do not do anything special, i.e. do not define any group, "git submodule foo" would act on path1, path2 and path3.

I think that is in line with the way how module_list aka "submodule--helper list" works.

Show 8 quoted lines

> +You can change the default group by configuring
> +submodule.defaultGroup. Once the default group is configured any
> +submodule operation without a specified set of submodules will use
> +the default group as the set to operate on.
> +
>  Submodules are composed from a so-called `gitlink` tree entry
>  in the main repository that refers to a particular commit object
>  within the inner repository that is completely separate.