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

Re: Patch that modifies git usage message

From
Stefan Beller <sbeller@google.com>
Date
May 1, 2015, 15:51 UTC
Message-ID
<CAGZ79kY1ZoYrVwVVqfyB+uMGsJo59qDxbDLgyo5qygSm=CUVhA@mail.gmail.com>
In-Reply-To
<CAKB+oNtYbJXNb2wGzJCdQ5Ru5fq3HzcapSqiTVC_34=xDnTb7Q@mail.gmail.com>
On Fri, May 1, 2015 at 4:01 AM, Alangi Derick <alangiderick@gmail.com> wrote:
Show 5 quoted lines
> This patch just modifies the "usage" word to "Usage" which enhances
> readability. Below is the patch
>
> Regards
> Alangi Derick Ndimnain

It's easier to have the patch in the email itself, this looks it's some form of attachment.

Checkout Documentation/SubmittingPatches (protip: get "git send-email" working, it will send in the preferred way by default for nearly any open source project using email based workflows.)

There are also some resources on the web, how to send patches, although it should be all covered in our Documentation, http://alblue.bandlem.com/2011/12/git-tip-of-week-patches-by-email.html

For the patch itself:

$ grep -r usage *.c builtin/*.c |wc -l 551 $ grep -r Usage *.c builtin/*.c |wc -l 3

The community agreed (maybe subconciously) to prefer lower case for the 'usage' string, so I don't think this is an improvement.

Previous: Alangi DerickNext: Alangi Derick
Message 2 of 10 in “Patch that modifies git usage message”
  1. Alangi DerickMay 1, 2015
  2. Stefan BellerMay 1, 2015
  3. Alangi DerickMay 1, 2015
  4. Junio C HamanoMay 1, 2015
  5. Alangi DerickMay 1, 2015
  6. Stefan BellerMay 1, 2015
  7. Eric SunshineMay 1, 2015
  8. Alangi DerickMay 1, 2015
  9. Eric SunshineMay 1, 2015
  10. Stefan BellerMay 1, 2015

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.