From: Junio C Hamano <gitster@pobox.com>
Date: Thu, 22 Jun 2017 20:20:59 GMT
Subject: Re: [PATCHv2] submodules: overhaul documentation
Message-ID: <xmqqlgojixjo.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <20170622174659.GA124061@google.com>

Brandon Williams <bmwill@google.com> writes:

> On 06/20, Stefan Beller wrote:
> ...
>> +The configuration of submodules
>> +-------------------------------
>> +
>> +Submodule operations can be configured using the following mechanisms
>> +(from highest to lowest precedence):
>> +
>> + * the command line for those commands that support taking submodule specs.
>> +
>> + * the configuration file `$GIT_DIR/config` in the superproject.
>> +
>> + * the `.gitmodules` file inside the superproject. A project usually
>> +   includes this file to suggest defaults for the upstream collection
>> +   of repositories.
>
> I dislike this last point.  Realistically we don't want this right?  So
> perhaps we shouldn't include it?

I am not sure if I follow.  Without .gitmodules, how would you, as a
downstream developer, bootstrap the whole thing?