git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [GSoC PATCH v3] bugreport: revert incorrect usage message change

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 30, 2026, 20:08 UTC
Message-ID
<xmqqldf9dqr6.fsf@gitster.g>
In-Reply-To
<20260330174131.456-5-24070721037@sithyd.siu.edu.in>
Smaran Jaianand <24070721037@sithyd.siu.edu.in> writes:
> Revert the previous change to keep it consistent with documentation.
> Based on the feedback, the usage string is intended to represent command syntax rather than provide a description.

You really do not have to post a patch to revert something that was rejected and did not get applied anywhere to our tree.

We frown upon a patch series that makes mistakes in an earlier step, only to fix them in a later step. The "git rebase -i" command helps us pretend to be more perfect developers than we actually are, whipping your patch series into a shape that builds one small step on top of another in a logical succession. Such a patch series is easier to understand than a history that faithfully records all the stumbles the developer made until they reached the final solution.

If you rebuilt your changes, while removing any parts that shouldn't be there, in an effort to pretend to be a more perfect developer, sometimes you might end up with an empty patch, and that is OK. You can just send a message that you are retracting the earlier patch and everybody would understand.

Thanks.
Previous: Smaran Jaianand
Message 7 of 7 in “bugreport: clarify usage message purpose”
  1. bugreport: clarify usage message purposeSmaran Jaianand, Mar 30, 2026
  2. bugreport: clarify usage message purposeSmaran Jaianand, Mar 30, 2026
  3. Karthik NayakMar 30, 2026
  4. Junio C HamanoMar 30, 2026
  5. bugreport: revert incorrect usage message changeSmaran Jaianand, Mar 30, 2026
  6. bugreport: revert incorrect usage message changeSmaran Jaianand, Mar 30, 2026
  7. Junio C HamanoMar 30, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.