git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Fangyi Zhou via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Fangyi Zhou <me@fangyi.io>
Subject: Re: [PATCH] bugreport: add missing closing bracket in usage line
Date: Fri, 16 Sep 2022 09:04:52 -0700	[thread overview]
Message-ID: <xmqq4jx7joez.fsf@gitster.g> (raw)
In-Reply-To: <pull.1329.git.git.1663326823401.gitgitgadget@gmail.com> (Fangyi Zhou via GitGitGadget's message of "Fri, 16 Sep 2022 11:13:43 +0000")

"Fangyi Zhou via GitGitGadget" <gitgitgadget@gmail.com> writes:

> From: Fangyi Zhou <me@fangyi.io>
>
> Signed-off-by: Fangyi Zhou <me@fangyi.io>
> ---
>     bugreport: add missing closing bracket in usage line
>     
>     Signed-off-by: Fangyi Zhou me@fangyi.io
>
> Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1329%2Ffangyi-zhou%2Fbugreport-usage-fix-v1
> Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1329/fangyi-zhou/bugreport-usage-fix-v1
> Pull-Request: https://github.com/git/git/pull/1329
>
>  builtin/bugreport.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/builtin/bugreport.c b/builtin/bugreport.c
> index 530895be55f..a4a5a88840d 100644
> --- a/builtin/bugreport.c
> +++ b/builtin/bugreport.c
> @@ -60,7 +60,7 @@ static void get_populated_hooks(struct strbuf *hook_info, int nongit)
>  }
>  
>  static const char * const bugreport_usage[] = {
> -	N_("git bugreport [-o|--output-directory <file>] [-s|--suffix <format>] [--diagnose[=<mode>]"),
> +	N_("git bugreport [-o|--output-directory <file>] [-s|--suffix <format>] [--diagnose[=<mode>]]"),
>  	NULL
>  };

OK, this came from aac0e8ff (builtin/bugreport.c: create
'--diagnose' option, 2022-08-12), which gets the SYNOPSIS
in the documentation right but misses the usage text.

An identical fix already exists as 63407051 (doc txt & -h
consistency: add missing "]" to bugreport "-h", 2022-09-05).

It may help the project more to help move the topic that contains it
forward by reviewing them, than independently coming up with an
identical fix.  The topic with the existing fix appears at

  https://lore.kernel.org/git/cover-00.34-00000000000-20220902T092734Z-avarab@gmail.com/

Thanks.

  reply	other threads:[~2022-09-16 16:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-16 11:13 [PATCH] bugreport: add missing closing bracket in usage line Fangyi Zhou via GitGitGadget
2022-09-16 16:04 ` Junio C Hamano [this message]
2022-09-16 16:31   ` Fangyi Zhou

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqq4jx7joez.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=me@fangyi.io \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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).