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

From: Glen Choo <chooglen@google.com>
Date: Jan 4, 2022, 22:20 UTC
Message-ID: <kl6ltuej6t3s.fsf@chooglen-macbookpro.roam.corp.google.com>
In-Reply-To: <CABPp-BFR29S-Pwq9LZEOjaCxozTV9mkUBpd2SLGwh7jNW+On4w@mail.gmail.com>

Elijah Newren <newren@gmail.com> writes:

Show 14 quoted lines

>> * 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?

>
> Can we squash the "fixup!" commit before merging?

Makes sense, I can squash it :)