From: Junio C Hamano <gitster@pobox.com>
To: Brandon Williams <bmwill@google.com>
Cc: Stefan Beller <sbeller@google.com>,
git@vger.kernel.org, jrnieder@gmail.com,
jonathantanmy@google.com
Subject: Re: [PATCHv2] submodules: overhaul documentation
Date: Thu, 22 Jun 2017 13:20:59 -0700 [thread overview]
Message-ID: <xmqqlgojixjo.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20170622174659.GA124061@google.com> (Brandon Williams's message of "Thu, 22 Jun 2017 10:46:59 -0700")
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?
next prev parent reply other threads:[~2017-06-22 20:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 18:53 [RFC/PATCH] submodules: overhaul documentation Stefan Beller
2017-06-13 19:29 ` Junio C Hamano
2017-06-13 21:06 ` Stefan Beller
2017-06-19 18:10 ` Brandon Williams
2017-06-20 21:42 ` Stefan Beller
2017-06-20 18:18 ` Jonathan Tan
2017-06-20 19:15 ` Stefan Beller
2017-06-20 22:56 ` [PATCHv2] " Stefan Beller
2017-06-21 3:45 ` Jonathan Tan
2017-06-21 17:25 ` Stefan Beller
2017-06-22 17:46 ` Brandon Williams
2017-06-22 18:54 ` Stefan Beller
2017-06-22 20:20 ` Junio C Hamano [this message]
2017-06-22 20:27 ` Stefan Beller
2017-06-22 21:03 ` Brandon Williams
2017-06-22 21:09 ` Stefan Beller
2017-06-22 21:01 ` [PATCHv3] " Stefan Beller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqlgojixjo.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=bmwill@google.com \
--cc=git@vger.kernel.org \
--cc=jonathantanmy@google.com \
--cc=jrnieder@gmail.com \
--cc=sbeller@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.