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

Re: [PATCH 1/2] submodule-config: keep shallow recommendation around

From
Stefan Beller <sbeller@google.com>
Date
May 26, 2016, 17:22 UTC
Message-ID
<CAGZ79kaFD=0ijNvs8B9V+KbhasqF1N6OoAVucR-Hf_hVN+b-dQ@mail.gmail.com>
In-Reply-To
<2022441346.44059.1464253372857.JavaMail.zimbra@ensimag.grenoble-inp.fr>

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

Show 19 quoted lines
> Hi Stefan,
>
> Stefan Beller <sbeller@google.com> writes:
>> [...]
>> @ -353,6 +354,15 @@ static int parse_config(const char *var, const char *value, void *data)
>>                  else if (parse_submodule_update_strategy(value,
>>                           &submodule->update_strategy) < 0)
>>                                  die(_("invalid value for %s"), var);
>> +        } else if (!strcmp(item.buf, "shallow")) {
>> +                if (!me->overwrite &&
>> +                         submodule->recommend_shallow != -1)
>
> Nit: You seems to be able to keep the whole condition on the same line:
>
>                 if (!me->overwrite && submodule->recommend_shallow != -1)
>
> If you want to keep it in two line, you might want to align it:
>                 if (!me->overwrite &&
>                     submodule->recommend_shallow != -1)
Thanks will fix!
>
> Thanks,
> Rémi
Previous: Remi Galan AlfonsoNext: Stefan Beller
Message 4 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.