All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew White <andrew.white@audinate.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Bug v2.23.0: command help for 'git push --recurse-submodules' is incorrect
Date: Mon, 27 Apr 2020 01:31:09 +0000	[thread overview]
Message-ID: <346FFB0C-7419-4E2D-B593-9F64F9403D11@audinatedante.onmicrosoft.com> (raw)

System: Mac OS X 10.12.6
git --version: git version 2.23.0

	% git push --\?
	error: unknown option `?'
	usage: git push [<options>] [<repository> [<refspec>...]]

	[snip]

	    --recurse-submodules[=(check|on-demand|no)]
	                          control recursive pushing of submodules

I read this as saying that the argument to recurse-submodules is optional.  However,

	% git push --recurse-submodules
	fatal: recurse-submodules missing parameter
	zsh: exit 128   git push --recurse-submodules

Manual page (git push --help) seems to indicate that argument to recurse-submodules is required.

I'm guessing it's just the command help that's incorrect.

--
Andrew


             reply	other threads:[~2020-04-27  1:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-27  1:31 Andrew White [this message]
2020-04-27  6:44 ` [PATCH] push: unset PARSE_OPT_OPTARG for --recurse-submodules Denton Liu
2020-04-27 12:02   ` Jeff King
2020-04-27 18:54     ` Junio C Hamano
2020-04-28  8:36       ` [PATCH] Use OPT_CALLBACK and OPT_CALLBACK_F Denton Liu
2020-04-28  8:45         ` Jeff King
2020-04-28 17:34           ` Junio C Hamano
2020-04-28 17:51       ` [PATCH] push: unset PARSE_OPT_OPTARG for --recurse-submodules Junio C Hamano
2020-04-28 22:59         ` Denton Liu

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=346FFB0C-7419-4E2D-B593-9F64F9403D11@audinatedante.onmicrosoft.com \
    --to=andrew.white@audinate.com \
    --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.