From: Glen Choo <chooglen@google.com>
To: Elijah Newren <newren@gmail.com>, Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Dec 2021, #06; Mon, 27)
Date: Tue, 04 Jan 2022 14:20:23 -0800 [thread overview]
Message-ID: <kl6ltuej6t3s.fsf@chooglen-macbookpro.roam.corp.google.com> (raw)
In-Reply-To: <CABPp-BFR29S-Pwq9LZEOjaCxozTV9mkUBpd2SLGwh7jNW+On4w@mail.gmail.com>
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?
>
> Can we squash the "fixup!" commit before merging?
Makes sense, I can squash it :)
next prev parent reply other threads:[~2022-01-04 22:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-28 0:16 What's cooking in git.git (Dec 2021, #06; Mon, 27) Junio C Hamano
2021-12-28 13:31 ` ab/cat-file (was: What's cooking in git.git (Dec 2021, #06; Mon, 27)) Ævar Arnfjörð Bjarmason
2021-12-28 13:40 ` hn/reftable-coverity-fixes " Ævar Arnfjörð Bjarmason
2021-12-28 14:35 ` ab/ambiguous-object-name " Ævar Arnfjörð Bjarmason
2021-12-28 15:20 ` ab/only-single-progress-at-once " Ævar Arnfjörð Bjarmason
2021-12-28 17:42 ` What's cooking in git.git (Dec 2021, #06; Mon, 27) Elijah Newren
2021-12-30 23:56 ` Junio C Hamano
2022-01-04 22:20 ` Glen Choo [this message]
2022-01-10 18:41 ` Junio C Hamano
2022-01-01 14:01 ` tl/ls-tree-oid-only (was: What's cooking in git.git (Dec 2021, #06; Mon, 27)) Teng Long
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=kl6ltuej6t3s.fsf@chooglen-macbookpro.roam.corp.google.com \
--to=chooglen@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=newren@gmail.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).