Git development
 help / color / mirror / Atom feed
From: Smaran Jaianand <24070721037@sithyd.siu.edu.in>
To: git@vger.kernel.org
Cc: smaran-jaianand <24070721037@sithyd.siu.edu.in>
Subject: [GSoC PATCH v3] bugreport: revert incorrect usage message change
Date: Mon, 30 Mar 2026 17:41:08 +0000	[thread overview]
Message-ID: <20260330174131.456-3-24070721037@sithyd.siu.edu.in> (raw)
In-Reply-To: <20260330064454.76833-1-24070721037@sithyd.siu.edu.in>

From: smaran-jaianand <24070721037@sithyd.siu.edu.in>

The usage string is intended to reflect command syntax rather than
describe functionality. Revert the previous change to keep it consistent
with documentation.

Signed-off-by: Smaran Jaianand <24070721037@sithyd.siu.edu.in>
---
v3: Revert previous change after feedback that usage strings should reflect command syntax rather than description.

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


-- 
* <https://www.facebook.com/symbiosis.official/>*  
<https://www.instagram.com/symbiosis.official/>  
<https://www.linkedin.com/school/symbiosis-international-university/>  
<https://x.com/symbiosistweets> 
 




**Disclaimer:* This email is 
governed by the Disclaimer Terms of SIU, which may be viewed at 
http://siu.edu.in/disclaimer.php <http://siu.edu.in/disclaimer.php>*



  parent reply	other threads:[~2026-03-30 18:07 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 ` [GSoC PATCH] " Junio C Hamano
2026-03-30 17:41 ` Smaran Jaianand [this message]
2026-03-30 17:41 ` [GSoC PATCH v3] bugreport: revert incorrect usage message change 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=20260330174131.456-3-24070721037@sithyd.siu.edu.in \
    --to=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