All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: <rsbecker@nexbridge.com>
Cc: "'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 19:17:21 +0900	[thread overview]
Message-ID: <xmqqcz8jmz4e.fsf@gitster.g> (raw)
In-Reply-To: <000b01d9112a$541c4de0$fc54e9a0$@nexbridge.com> (rsbecker@nexbridge.com's message of "Fri, 16 Dec 2022 03:42:19 -0500")

<rsbecker@nexbridge.com> writes:

> 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".
>> ...
>
> 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?

I suspect it is the same issue as the one that triggered

  https://lore.kernel.org/git/f805f2da-a7e1-9fde-cc0a-04a30f79c9af@cs-ware.de/

which came out recently?

  reply	other threads:[~2022-12-16 10:17 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
2022-12-16 10:17   ` Junio C Hamano [this message]
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=xmqqcz8jmz4e.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=christoph.nemmaier@cpp.canon \
    --cc=git@vger.kernel.org \
    --cc=rsbecker@nexbridge.com \
    /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.