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

From: Remi Galan Alfonso <remi.galan-alfonso@ensimag.grenoble-inp.fr>
Date: May 26, 2016, 09:07 UTC
Message-ID: <135840520.44198.1464253655936.JavaMail.zimbra@ensimag.grenoble-inp.fr>
In-Reply-To: <20160526000633.27223-3-sbeller@google.com>

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

Stefan Beller <sbeller@google.com> writes:

Show 7 quoted lines

> [...]
>  '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...

Show 5 quoted lines

> +--[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