From: Junio C Hamano <gitster@pobox.com>
To: Heiko Voigt <hvoigt@hvoigt.net>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
Stefan Beller <sbeller@google.com>,
git@vger.kernel.org, Jens Lehmann <Jens.Lehmann@web.de>
Subject: Re: [RFD/PATCH] submodule doc: describe where we can configure them
Date: Mon, 09 May 2016 09:19:44 -0700 [thread overview]
Message-ID: <xmqqlh3jxkyn.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20160508220127.GB59077@book.hvoigt.net> (Heiko Voigt's message of "Mon, 9 May 2016 00:01:28 +0200")
Heiko Voigt <hvoigt@hvoigt.net> writes:
>> > - When upstream adds a new submodule, I have to do the same manual
>> > work to change the options for that new submodule.
>>
>> Because a new module is not automatically "init"ed by default?
>>
>> Isn't "config only" vs "config with gitmodules fallback" orthogonal
>> to that issue?
>
> What do you mean with "orthogonal to that issue"? AFAICS a gitmodule
> fallback does not have that issue.
>
> Actually I would see it more like:
> .gitmodule is the default and .git/config a possibility to override.
The way I read Jonathan's "I have to do the same manual..." above is:
Back when I cloned, the upstream had one submodule A. I didn't like
some aspect of the configuration for that submodule so I did a
customization in [submodule "A"] section of .git/config for it.
Now the upstream added another submodule B. I want a tweak similar
to what I did to A applied to this one, but that would mean I need
to edit the entry in .git/config copied by "init" from .gitmodules.
I do not see how difference between ".git/config is the only source
of truth" or ".git/config overrides what is in .gitmodules" would
matter to the above scenario.
next prev parent reply other threads:[~2016-05-09 16:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-03 23:26 [RFD/PATCH] submodule doc: describe where we can configure them Stefan Beller
2016-05-03 23:56 ` Jonathan Nieder
2016-05-04 0:59 ` Stefan Beller
2016-05-04 15:01 ` Heiko Voigt
2016-05-04 20:50 ` Stefan Beller
2016-05-08 21:54 ` Heiko Voigt
2016-05-09 17:32 ` Stefan Beller
2016-05-11 16:54 ` Heiko Voigt
2016-05-04 21:13 ` Junio C Hamano
2016-05-08 22:01 ` Heiko Voigt
2016-05-09 16:19 ` Junio C Hamano [this message]
2016-05-11 15:50 ` Heiko Voigt
2016-05-04 20:48 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqlh3jxkyn.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=Jens.Lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=hvoigt@hvoigt.net \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).