From: Junio C Hamano <gitster@pobox.com>
To: Michal Suchanek <msuchanek@suse.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-push: more visibility for -q option
Date: Fri, 20 Oct 2023 13:08:04 -0700 [thread overview]
Message-ID: <xmqqwmvhoy57.fsf@gitster.g> (raw)
In-Reply-To: <20231020184627.14336-1-msuchanek@suse.de> (Michal Suchanek's message of "Fri, 20 Oct 2023 20:45:21 +0200")
Michal Suchanek <msuchanek@suse.de> writes:
> The -v option listed at the top as option al parameter while -q is not.
"as option al parameter" - ECANNOTPARSE. Probably
The `-v` option is shown in the SYNOPSIS section near the top,
but `-q` is not shown anywhere there.
or something, I think. I agree showing it next to "-v" would make
the most sense.
>
> List -q alongside -v.
>
> Signed-off-by: Michal Suchanek <msuchanek@suse.de>
> ---
> Documentation/git-push.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt
> index 5b4edaf4a8..003bc7d9ce 100644
> --- a/Documentation/git-push.txt
> +++ b/Documentation/git-push.txt
> @@ -10,7 +10,7 @@ SYNOPSIS
> --------
> [verse]
> 'git push' [--all | --branches | --mirror | --tags] [--follow-tags] [--atomic] [-n | --dry-run] [--receive-pack=<git-receive-pack>]
> - [--repo=<repository>] [-f | --force] [-d | --delete] [--prune] [-v | --verbose]
> + [--repo=<repository>] [-f | --force] [-d | --delete] [--prune] [-q | --quiet] [-v | --verbose]
Yup, the change makes sense. We may want to wrap the first line to
a more reasonable length in a separate commit, and when that
happens, we probably would want to start [-v] [-q] on a separate
line as well, but for now this would do.
next prev parent reply other threads:[~2023-10-20 20:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 18:45 [PATCH] git-push: more visibility for -q option Michal Suchanek
2023-10-20 20:05 ` Eric Sunshine
2023-10-20 20:08 ` Junio C Hamano [this message]
2023-10-30 10:40 ` Michal Suchánek
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=xmqqwmvhoy57.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=msuchanek@suse.de \
/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 NNTP newsgroup(s).