Oh, I overlooked the question for the git version: As contained in my first mail, it is 2.38.1.windows.1. I hear from colleagues tells me that 2.23 is working OK. I intend to verify this. Canon Production Printing Germany GmbH & Co. KG P.O. Box 1260, 85581 Poing Siemensallee 2, 85586 Poing Germany | www.cpp.canon Canon Production Printing Germany GmbH & Co. KG. The company is a limited partnership with its registered office in Poing Trade Register HRA 100955 (Amtsgericht München) - WEEE-Reg. - No. DE 888 05 443 General Partner: Canon Production Printing Geschäftsführungsgesellschaft mbH Registered Office: Poing Trade Register HRB 206480 (Amtsgericht München) Executive Officer: Johann Meyer This message and attachment(s) are intended solely for use by the addressee and may contain information that is privileged, confidential or otherwise exempt from disclosure under applicable law. If you are not the intended recipient or agent thereof responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by telephone or with a 'reply' message and delete the message and its attachment(s), if any, from your system(s). Thank you for your co-operation. -----Ursprüngliche Nachricht----- Von: Nemmaier, Christoph Gesendet: Freitag, 16. Dezember 2022 11:43 An: rsbecker@xxxxxxxxxxxxx; git@xxxxxxxxxxxxxxx Betreff: AW: PROBLEM: "git pull -v" fails with exit code denoting a submodule syntax error Hi, no alias - the command is used by TortoiseSVN, like in: git.exe pull --progress -v --no-rebase "origin" >From gitlab.ops.oce.net:nemmaiec/cpposatest = [up to date] master -> origin/master 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>...] I verified that the -v parameter is the culprit. Today I also found out that this only happens if .gitconfig contains a [submodule] section setting "recurse = true". Meanwhile a colleague of mine stumbled over another problem that (he claims) was not there until he upgraded git: GitExtensions uses "--jobs=0", which does not work anymore. But, of course, that's obviously a GitExtensions problem, just never having showed up before. Christoph git did not exit cleanly (exit code 1) (3610 ms @ 16.12.2022 11:33:35) -----Ursprüngliche Nachricht----- Von: rsbecker@xxxxxxxxxxxxx <rsbecker@xxxxxxxxxxxxx> Gesendet: Freitag, 16. Dezember 2022 09:42 An: Nemmaier, Christoph <christoph.nemmaier@cpp.canon>; git@xxxxxxxxxxxxxxx Betreff: RE: PROBLEM: "git pull -v" fails with exit code denoting a submodule syntax error On December 16, 2022 3:28 AM, Nemmaier, Christoph wrote: >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] >N|[--[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
