Patch that modifies git usage message
From: Alangi Derick <hidden>
Date: 2016-06-15 23:04:36
This patch just modifies the "usage" word to "Usage" which enhances readability. Below is the patch Regards Alangi Derick Ndimnain
3 messages, 2 authors, 2016-06-15 · open the first message on its own page
From: Alangi Derick <hidden>
Date: 2016-06-15 23:04:36
This patch just modifies the "usage" word to "Usage" which enhances readability. Below is the patch Regards Alangi Derick Ndimnain
From: Stefan Beller <hidden>
Date: 2016-06-15 23:04:36
On Fri, May 1, 2015 at 4:01 AM, Alangi Derick [off-list ref] wrote:
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.
From: Alangi Derick <hidden>
Date: 2016-06-15 23:04:36
I am saying so because there are some strings with upper case letters and others with lower case letters. So there is no consistency. That is why i wanted to keep the consistency by correcting the letters which are to be corrected and allow the once which are to be allowed. Regards Alangi Derick Ndimnain On Fri, May 1, 2015 at 4:51 PM, Stefan Beller [off-list ref] wrote:
On Fri, May 1, 2015 at 4:01 AM, Alangi Derick [off-list ref] wrote:quoted
This patch just modifies the "usage" word to "Usage" which enhances readability. Below is the patch Regards Alangi Derick NdimnainIt'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.