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

RE: PROBLEM: "git pull -v" fails with exit code denoting a submodule syntax error

From
rsbecker@nexbridge.com <rsbecker@nexbridge.com>
Date
Dec 16, 2022, 08:42 UTC
Message-ID
<000b01d9112a$541c4de0$fc54e9a0$@nexbridge.com>
In-Reply-To
<AM8P195MB0820A54FEA04231D440F74D780E69@AM8P195MB0820.EURP195.PROD.OUTLOOK.COM>
On December 16, 2022 3:28 AM, Nemmaier, Christoph wrote:
Show 36 quoted lines
>I expected "git pull -v" to simply work and exit correctly without telling me the
>syntax of "git submodule".
>
>What happened instead? (Actual behavior)
>
>This:
>> From gitlab.ops.oce.net:nemmaiec/cpposa
>> = [up to date]      develop/1.0 -> origin/develop/1.0
>> Already up to date.
>> usage: git submodule [--quiet] [--cached]
>>    or: git submodule [--quiet] add [-b <branch>] [-f|--force] [--name <name>] [--
>reference <repository>] [--] <repository> [<path>]
>>    or: git submodule [--quiet] status [--cached] [--recursive] [--] [<path>...]
>>    or: git submodule [--quiet] init [--] [<path>...]
>>    or: git submodule [--quiet] deinit [-f|--force] (--all| [--] <path>...)
>>    or: git submodule [--quiet] update [--init [--filter=<filter-spec>]] [--remote] [-
>N|--no-fetch] [-f|--force] [--checkout|--merge|--rebase] [--[no-]recommend-
>shallow] [--reference <repository>] [--recursive] [--[no-]single-branch] [--]
>[<path>...]
>>    or: git submodule [--quiet] set-branch (--default|--branch <branch>) [--]
><path>
>>    or: git submodule [--quiet] set-url [--] <path> <newurl>
>>    or: git submodule [--quiet] summary [--cached|--files] [--summary-limit <n>]
>[commit] [--] [<path>...]
>>    or: git submodule [--quiet] foreach [--recursive] <command>
>>    or: git submodule [--quiet] sync [--recursive] [--] [<path>...]
>>    or: git submodule [--quiet] absorbgitdirs [--] [<path>...]
>
>What's different between what you expected and what actually happened?
>
>The text I quoted above, and an exit with error code.
>
>Anything else you want to add:
>
>The '-v' parameter is used by TortoiseGit and GitExtensions, which now both croak
>on pulling.
Hi Christoph,

I have gone back to git 2.36.0 and cannot find support for the -v submodule command parameter. At what version did this last work for you? Do you have a git alias in effect that might be adding -v? --Randall

Previous: Nemmaier, ChristophNext: Junio C Hamano
Message 2 of 10 in “PROBLEM: "git pull -v" fails with exit code denoting a submodule syntax error”
  1. Nemmaier, ChristophDec 16, 2022
  2. rsbecker@nexbridge.comDec 16, 2022
  3. Junio C HamanoDec 16, 2022
  4. AW: PROBLEM: "git pull -v" fails with exit code denoting a submodule syntax errorNemmaier, Christoph, Dec 16, 2022
  5. rsbecker@nexbridge.comDec 17, 2022
  6. AW: PROBLEM: "git pull -v" fails with exit code denoting a submodule syntax errorNemmaier, Christoph, Dec 19, 2022
  7. Junio C HamanoDec 19, 2022
  8. AW: AW: PROBLEM: "git pull -v" fails with exit code denoting a submodule syntax errorNemmaier, Christoph, Dec 20, 2022
  9. AW: PROBLEM: "git pull -v" fails with exit code denoting a submodule syntax errorNemmaier, Christoph, Dec 16, 2022
  10. AW: PROBLEM: "git pull -v" fails with exit code denoting a submodule syntax errorNemmaier, Christoph, Dec 16, 2022

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.