Re: What's cooking in git.git (Dec 2021, #06; Mon, 27)

From: Junio C Hamano <gitster@pobox.com>
Date: Jan 10, 2022, 18:41 UTC
Message-ID: <xmqqsftvzb4u.fsf@gitster.g>
In-Reply-To: <kl6ltuej6t3s.fsf@chooglen-macbookpro.roam.corp.google.com>

Glen Choo <chooglen@google.com> writes:

Show 18 quoted lines

> Elijah Newren <newren@gmail.com> writes:
>
>>> * gc/branch-recurse-submodules (2021-12-25) 7 commits
>>>  - fixup! branch: add --recurse-submodules option for branch creation
>>>  - branch: add --recurse-submodules option for branch creation
>>>  - builtin/branch: clean up action-picking logic in cmd_branch()
>>>  - branch: add a dry_run parameter to create_branch()
>>>  - branch: make create_branch() always create a branch
>>>  - branch: move --set-upstream-to behavior to dwim_and_setup_tracking()
>>>  - Merge branch 'js/branch-track-inherit' into gc/branch-recurse-submodules
>>>  (this branch uses js/branch-track-inherit.)
>>>
>>>  "git branch" learned the "--recurse-submodules" option.
>>>
>>>  Will merge to 'next'?
>>>  source: <20211220233459.45739-1-chooglen@google.com>
>
> Is there anything in particular blocking this series? e.g. does it need more review?

An ack or two from those who gave their feedbacks on previous rounds, which hasn't happened since v3, I think.

>> Can we squash the "fixup!" commit before merging?
>
> Makes sense, I can squash it :)