From: Duy Nguyen <email@example.com>
To: Ben Avison <firstname.lastname@example.org>
Cc: Git Mailing List <email@example.com>
Subject: Re: [PATCH] clone: add `--remote-submodules` flag
Date: Sat, 18 May 2019 18:40:55 +0700 [thread overview]
Message-ID: <CACsJy8BypLygJGW67mtomL=VLQLVuPSsYTx-3+Dp_Zg-hkSVpA@mail.gmail.com> (raw)
On Fri, May 17, 2019 at 12:50 AM Ben Avison <firstname.lastname@example.org> wrote:
> On 16/05/2019 12:31, Duy Nguyen wrote:
> > On Tue, May 14, 2019 at 2:46 AM Ben Avison <email@example.com> wrote:
> >> When using `git clone --recurse-submodules` there was previously no way to
> >> pass a `--remote` switch to the implicit `git submodule update` command for
> >> any use case where you want the submodules to be checked out on their
> >> remote-tracking branch rather than with the SHA-1 recorded in the superproject.
> > Are there any other submodule options that could be useful passing
> > from git-clone as well? What I'm getting at is, if there are multiple
> > of them, perhaps we need a different/generic approach than introducing
> > a bunch of --<something>-submodules. But of course if --remote is the
> > only useful one left, then it's moot.
> That's an interesting point. However, for many of the switches, it only
> makes sense to set them one way when you're calling `git submodule
> update` within `git clone --recurse-submodules`.
> In summary, the most significant omission is --remote IMHO, though there
> may be an argument for adding a small number of others.
Great! Thanks for checking.
prev parent reply other threads:[~2019-05-18 11:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 17:59 [PATCH] clone: add `--remote-submodules` flag Ben Avison
2019-05-13 21:12 ` Ævar Arnfjörð Bjarmason
2019-05-14 18:38 ` Ben Avison
2019-05-19 14:26 ` [PATCH v2] " Ben Avison
2019-05-16 11:31 ` [PATCH] " Duy Nguyen
2019-05-16 17:50 ` Ben Avison
2019-05-18 11:40 ` Duy Nguyen [this message]
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:
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 \
* 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
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).