From: Glen Choo <chooglen@google.com>
Date: Fri, 09 Sep 2022 16:56:17 GMT
Subject: Re: What's cooking in git.git (Sep 2022, #01; Mon, 5)
Message-ID: <kl6lmtb88p1q.fsf@chooglen-macbookpro.roam.corp.google.com>
In-Reply-To: <xmqqpmg5rehf.fsf@gitster.g>

Junio C Hamano <gitster@pobox.com> writes:

> Glen Choo <chooglen@google.com> writes:
>
>> Junio C Hamano <gitster@pobox.com> writes:
>>
>>> * gc/submodule-propagate-branches (2022-08-29) 6 commits
>>>  - clone, submodule update: check out branches
>>>  - submodule--helper: refactor up-to-date criterion
>>>  - submodule: return target of submodule symref
>>>  - t5617: drop references to remote-tracking branches
>>>  - repo-settings: add submodule_propagate_branches
>>>  - clone: teach --detach option
>>>
>>>  "git clone --recurse-submodules" and "git submodule update" learns
>>>  to honor the "propagete branches" option.
>>>
>>>  Needs review.
>>>  source: <pull.1321.git.git.1661806456.gitgitgadget@gmail.com>
>>
>> I suggest renaming the branch - the config "submodule.propagateBranches"
>> will be used by many more commands in the future, several of which will
>> probably be authored by me :)
>
> OK.  So this is a "clone" and "update" part of the larger topic?

Yup; submodule.propagateBranches is the "branching" part of the
submodule UX work that the Google team is working on.

>> Maybe gc/submodule-update-with-branches? Or
>> gc/recursive-clone-with-branches.
>
> Both sound good suggestions.

Ok, I think gc/recursive-clone-with-branches captures the intent better
(the improvements to `git submodule update` are more of an
implementation detail).

Thanks!