From: Junio C Hamano <gitster@pobox.com>
To: "Nemmaier, Christoph" <christoph.nemmaier@cpp.canon>
Cc: "rsbecker@nexbridge.com" <rsbecker@nexbridge.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: AW: PROBLEM: "git pull -v" fails with exit code denoting a submodule syntax error
Date: Tue, 20 Dec 2022 08:27:13 +0900 [thread overview]
Message-ID: <xmqqzgbj2cvi.fsf@gitster.g> (raw)
In-Reply-To: <AM8P195MB0820F8606B7B7A2B91442C4A80E59@AM8P195MB0820.EURP195.PROD.OUTLOOK.COM> (Christoph Nemmaier's message of "Mon, 19 Dec 2022 08:02:39 +0000")
"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-ware.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@cs-ware.de> 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'.
next prev parent reply other threads:[~2022-12-19 23:27 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
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 [this message]
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=xmqqzgbj2cvi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).