From: Junio C Hamano <gitster@pobox.com>
To: Glen Choo <chooglen@google.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2022, #01; Mon, 5)
Date: Thu, 08 Sep 2022 09:57:16 -0700 [thread overview]
Message-ID: <xmqqpmg5rehf.fsf@gitster.g> (raw)
In-Reply-To: <kl6ly1uu94ca.fsf@chooglen-macbookpro.roam.corp.google.com> (Glen Choo's message of "Wed, 07 Sep 2022 16:01:25 -0700")
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?
> Maybe gc/submodule-update-with-branches? Or
> gc/recursive-clone-with-branches.
Both sound good suggestions.
next prev parent reply other threads:[~2022-09-08 16:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 6:49 What's cooking in git.git (Sep 2022, #01; Mon, 5) Junio C Hamano
2022-09-06 14:17 ` en/remerge-diff-fixes (Was: Re: What's cooking in git.git (Sep 2022, #01; Mon, 5)) Elijah Newren
2022-09-07 16:17 ` en/remerge-diff-fixes Junio C Hamano
2022-09-07 23:01 ` What's cooking in git.git (Sep 2022, #01; Mon, 5) Glen Choo
2022-09-08 16:57 ` Junio C Hamano [this message]
2022-09-09 16:56 ` Glen Choo
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqpmg5rehf.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=chooglen@google.com \
--cc=git@vger.kernel.org \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.