Great, THX. 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: Junio C Hamano <jch2355@xxxxxxxxx> Im Auftrag von Junio C Hamano Gesendet: Dienstag, 20. Dezember 2022 00:27 An: Nemmaier, Christoph <christoph.nemmaier@cpp.canon> Cc: rsbecker@xxxxxxxxxxxxx; git@xxxxxxxxxxxxxxx Betreff: Re: AW: PROBLEM: "git pull -v" fails with exit code denoting a submodule syntax error "Nemmaier, Christoph" <christoph.nemmaier@cpp.canon> writes: >> ... >>> >>>I suspect it is the same issue as the one that triggered >>> >>> >>https://lore.kernel.org/git/f805f2da-a7e1-9fde-cc0a-04a30f79c9af@cs-wa >>re.de/ >>> >>>which came out recently? >> >>If that is the case, perhaps the -v needs to be documented in the online help if/when this condition is fixed. >> > > > Good morning, > > it pretty sure is. The doc goes like: > >> -v >>--verbose >> >> Pass --verbose to git-fetch and git-merge. > > Intentionally or not, git-submodule is not listed. > > Anyway, I think the doc is correct, as git submodule doesn't know > '-v'. So either the internal call should drop '-v', or 'submodule' > should ignore it. Yes, <f805f2da-a7e1-9fde-cc0a-04a30f79c9af@xxxxxxxxxx> cited above is exactly about doing that. The resulting 6f65f847 (submodule: accept -v for the update command, 2022-12-10) is about to hit 'next'.
