On Fri, May 17, 2019 at 12:50 AM Ben Avison <bavison@xxxxxxxxxxxxxx> wrote: > > On 16/05/2019 12:31, Duy Nguyen wrote: > > On Tue, May 14, 2019 at 2:46 AM Ben Avison <bavison@xxxxxxxxxxxxxx> 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. -- Duy>>
