Re: [PATCH v4 3/4] submodule: support running in multiple worktree setup

From: Junio C Hamano <gitster@pobox.com>
Date: Jul 25, 2016, 15:46 UTC
Message-ID: <xmqqwpk97mbn.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <CAGZ79kbH=ywi7sXUz5KKyRqo-Eg4RF3W9pf53rzKE-oz5-PW1Q@mail.gmail.com>

Stefan Beller <sbeller@google.com> writes:

Show 10 quoted lines

> On Fri, Jul 22, 2016 at 9:55 AM, Junio C Hamano <gitster@pobox.com> wrote:
>>
>>  * submodule.$name.update, submodule.$name.ignore,
>>    submodule.$name.branch, etc. would need to be all different among
>>    worktrees of the superproject, as that is the whole point of
>>    being able to work on separate branches of the superproject in
>>    separate worktrees.
>
> What do you mean by "would need". The ability to be different or rather
> the veto of an 'inheritance' of defaults from the repository configuration?

They have to be able to represent different settings per worktree that checks out different branches/commits of superproject. They may happen to be set the same, but they do not have to be.

Is what I meant.