From: Karthik Nayak Date: Mon, 30 Mar 2026 09:32:12 GMT Subject: Re: [GSoC PATCH v2] bugreport: clarify usage message purpose Message-ID: In-Reply-To: <20260330065053.76919-3-24070721037@sithyd.siu.edu.in> Smaran Jaianand <24070721037@sithyd.siu.edu.in> writes: > From: smaran-jaianand <24070721037@sithyd.siu.edu.in> > > v2: Fix spacing in usage message (add missing space and remove > trailing whitespace). Version related changes should either go into the cover letter or below the '---' in the commit. I would recommend reading the following documentation - Documentation/SubmittingPatches - Documentation/CodingGuidelines - Documentation/MyFirstContribution.adoc > > Add a brief description of the bugreport command to improve > clarity of the usage message. > The git command adds command description to the 'NAME' header within the documentation. For 'git-bugreport(1)' you can find this in 'Documentation/git-bugreport.adoc'. > Signed-off-by: smaran-jaianand <24070721037@sithyd.siu.edu.in> > 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..6b1d1accb1 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) ]\n" > + N_("git bugreport - create a bug report with diagnostic information\n" > + " [(-o | --output-directory) ]\n" > " [(-s | --suffix) | --no-suffix]\n" > " [--diagnose[=]]"), > NULL > -- > 2.43.0 > > > -- > * * > > > > > > > > > **Disclaimer:* This email is > governed by the Disclaimer Terms of SIU, which may be viewed at > http://siu.edu.in/disclaimer.php *