From: <rsbecker@nexbridge.com>
To: "'Nemmaier, Christoph'" <christoph.nemmaier@cpp.canon>,
<git@vger.kernel.org>
Subject: RE: PROBLEM: "git pull -v" fails with exit code denoting a submodule syntax error
Date: Fri, 16 Dec 2022 03:42:19 -0500 [thread overview]
Message-ID: <000b01d9112a$541c4de0$fc54e9a0$@nexbridge.com> (raw)
In-Reply-To: <AM8P195MB0820A54FEA04231D440F74D780E69@AM8P195MB0820.EURP195.PROD.OUTLOOK.COM>
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] [--[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
next prev parent reply other threads:[~2022-12-16 8:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 8:27 PROBLEM: "git pull -v" fails with exit code denoting a submodule syntax error Nemmaier, Christoph
2022-12-16 8:42 ` rsbecker [this message]
2022-12-16 10:17 ` Junio C Hamano
2022-12-16 10:49 ` AW: " Nemmaier, Christoph
2022-12-17 1:03 ` rsbecker
2022-12-19 8:02 ` AW: " Nemmaier, Christoph
2022-12-19 23:27 ` Junio C Hamano
2022-12-20 7:37 ` AW: " Nemmaier, Christoph
2022-12-16 10:43 ` Nemmaier, Christoph
2022-12-16 11:24 ` Nemmaier, Christoph
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000b01d9112a$541c4de0$fc54e9a0$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=christoph.nemmaier@cpp.canon \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.