Thread (7 messages) 7 messages, 2 authors, 2016-06-16

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

From: Remi Galan Alfonso <hidden>
Date: 2016-06-16 02:19:36

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

Stefan Beller [off-list ref] writes:
[...]
 '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...
+--[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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help