Re: [PATCH 2/2] submodule update: learn `--[no-]recommend-shallow` option

On Thu, May 26, 2016 at 2:07 AM, Remi Galan Alfonso
[off-list ref] wrote:

You forgot to update from recommend-depth to recommend-shallow

Stefan Beller [off-list ref] writes:

quoted

[...]
 'git submodule' [--quiet] init [--] [<path>...]
 'git submodule' [--quiet] deinit [-f|--force] (--all|[--] <path>...)
 'git submodule' [--quiet] update [--init] [--remote] [-N|--no-fetch]
-              [-f|--force] [--rebase|--merge] [--reference <repository>]
-              [--depth <depth>] [--recursive] [--jobs <n>] [--] [<path>...]
+              [--[no-]recommended-depth] [-f|--force] [--rebase|--merge]

Here...

quoted

+--[no-]recommended-depth::
+        This option is only valid for the update command.
+        The initial clone of a submodule will use the recommended
+        `submodule.<name>.depth` as provided by the .gitmodules file.
+

... and here.

Thanks,
Rémi

Thanks for the review,
these will be fixed in a reroll.

Thanks,
Stefan