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

Re: [PATCHv2] pull: honor submodule.recurse config option

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 7, 2017, 00:54 UTC
Message-ID
<xmqqbmmn2ur7.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<c3842980-22ef-5a8c-2895-90c48a97ed71@suse.de>
Nicolas Morey-Chaisemartin <NMoreyChaisemartin@suse.de> writes:
Show 6 quoted lines
>> If it is not the latter, perhaps we may want to flip the order of
>> config parsing and option parsing around?  That will allow us to fix
>> the handling of autostash thing to use only one variable, and also
>> fix your patch to do the right thing.
>
> I see what you mean.
Show 8 quoted lines
> It looks like switching the code around works but I think there
> still needs to be 2 variables for autstash for this piece of code:
>
>     if (!opt_rebase && opt_autostash != -1)
>         die(_("--[no-]autostash option is only valid with --rebase."));
>
> The config option should not cause git pull to die when not using
> --rebase, the CLI option should.

Ah, OK. That is a worthwhile observation that needs to be recorded in the log message of a commit that flips the order of option/config parsing.

Thanks.
Previous: Nicolas Morey-Chaisemartin
Message 4 of 4 in “[PATCHv2] pull: honor submodule.recurse config option”
  1. Nicolas Morey-ChaisemartinSep 4, 2017
  2. Junio C HamanoSep 6, 2017
  3. Nicolas Morey-ChaisemartinSep 6, 2017
  4. Junio C HamanoSep 7, 2017

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.