git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Stefan Beller <sbeller@google.com>
Date
May 26, 2016, 17:29 UTC
Message-ID
<CAGZ79kY1yWp0r1XzRUVxnFC3jee1w3LtXUkx5NUjNoBWbbXMhg@mail.gmail.com>
In-Reply-To
<135840520.44198.1464253655936.JavaMail.zimbra@ensimag.grenoble-inp.fr>

On Thu, May 26, 2016 at 2:07 AM, Remi Galan Alfonso <remi.galan-alfonso@ensimag.grenoble-inp.fr> wrote:

Show 23 quoted lines
> You forgot to update from recommend-depth to recommend-shallow
>
> Stefan Beller <sbeller@google.com> 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

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

Thanks, Stefan

Previous: Remi Galan AlfonsoNext: Junio C Hamano
Message 7 of 11 in “[PATCHv2 0/2] Submodule shallow recommendation [WAS: Submodules: have a depth field in the .gitmodules file]”
  1. Stefan BellerMay 26, 2016
  2. 1/2 submodule-config: keep shallow recommendation aroundStefan Beller, May 26, 2016
  3. Remi Galan AlfonsoMay 26, 2016
  4. Stefan BellerMay 26, 2016
  5. 2/2 submodule update: learn `--[no-]recommend-shallow` optionStefan Beller, May 26, 2016
  6. Remi Galan AlfonsoMay 26, 2016
  7. Stefan BellerMay 26, 2016
  8. Junio C HamanoMay 26, 2016
  9. Stefan BellerMay 26, 2016
  10. Junio C HamanoMay 26, 2016
  11. Stefan BellerMay 26, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.