From: Junio C Hamano <gitster@pobox.com>
To: Smaran Jaianand <24070721037@sithyd.siu.edu.in>
Cc: git@vger.kernel.org
Subject: Re: [GSoC PATCH] bugreport: clarify usage message purpose
Date: Mon, 30 Mar 2026 07:56:54 -0700 [thread overview]
Message-ID: <xmqqjyutfjrd.fsf@gitster.g> (raw)
In-Reply-To: <20260330064454.76833-1-24070721037@sithyd.siu.edu.in> (Smaran Jaianand's message of "Mon, 30 Mar 2026 06:44:44 +0000")
Smaran Jaianand <24070721037@sithyd.siu.edu.in> writes:
> From: smaran-jaianand <24070721037@sithyd.siu.edu.in>
>
> Add a brief description of the bugreport command to improve
> clarity of the usage message.
>
> Signed-off-by: smaran-jaianand <24070721037@sithyd.siu.edu.in>
> ---
> builtin/bugreport.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/builtin/bugreport.c b/builtin/bugreport.c
> index f78c3f2aed..3b3fdd4dfb 100644
> --- a/builtin/bugreport.c
> +++ b/builtin/bugreport.c
> @@ -56,7 +56,8 @@ static void get_populated_hooks(struct strbuf *hook_info, int nongit)
> }
>
> static const char * const bugreport_usage[] = {
> - N_("git bugreport [(-o | --output-directory) <path>]\n"
> + N_("git bugreport -create a bug report with diagnostic information \n"
> + " [(-o | --output-directory) <path>]\n"
> " [(-s | --suffix) <format> | --no-suffix]\n"
> " [--diagnose[=<mode>]]"),
> NULL
> --
> 2.43.0
This is wrong. The usage string is to show "usage". Unless your
users type
$ git bugreport -create a bug ...
from their command line, the first line that you added does not
belong there.
In general, these should match what is in the synopsis section of
the manpage (i.e., "git help bugreport" output), and there is even
a test to ensure they do not diverge from each other (iirc, t0450).
next prev parent reply other threads:[~2026-03-30 14:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 6:44 [GSoC PATCH] bugreport: clarify usage message purpose Smaran Jaianand
2026-03-30 6:50 ` [GSoC PATCH v2] " Smaran Jaianand
2026-03-30 9:32 ` Karthik Nayak
2026-03-30 14:56 ` Junio C Hamano [this message]
2026-03-30 17:41 ` [GSoC PATCH v3] bugreport: revert incorrect usage message change Smaran Jaianand
2026-03-30 17:41 ` Smaran Jaianand
2026-03-30 20:08 ` Junio C Hamano
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=xmqqjyutfjrd.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=24070721037@sithyd.siu.edu.in \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox