Re: [PATCH v5 2/2] submodule: pass on http.extraheader config settings

From: Junio C Hamano <gitster@pobox.com>
Date: Apr 28, 2016, 22:47 UTC
Message-ID: <xmqqshy52vwb.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <CAGZ79kY1TB9sZpZcihiC5rPmbf8qD9KsAZsWDcon+UnHG7R3jw@mail.gmail.com>

Stefan Beller <sbeller@google.com> writes:

Show 9 quoted lines

> It doesn't even have to be a submodule related thing at all.
>
> I can imagine that `git gc` could learn to walk nested repos
> (not submodules, just repos on disk inside the work tree).
> And for that use case we'd maybe want to have a setting
> to pack the nested repos more aggressively than the toplevel repo.
>
> (Not sure if there would be a use case or such a thing, but it is the
> first I came up with)

I do not think we are in the business of mucking with "dump of unrelated collections of repositories, whose inter-relationship the user did not tell us anything about".

I however can foresee a value in "git gc --recurse-submodules", and I could see users may want to gc different submodules in different ways (which again brings us back to your "submodule group" thing).