Re: Patch that modifies git usage message

On Fri, May 1, 2015 at 9:38 AM, Alangi Derick wrote: > Can't i change the "cannot" to "Cannot"? Or is there a problem with > that one too? Well maybe you can make a strong argument for changing it like you'd find it inconsistencies in different spots. If you're in the game just to change a thing

Re: Patch that modifies git usage message

Stefan Beller writes: > 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. I tend to agree with

Re: Patch that modifies git usage message

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 Nd

Patch that modifies git usage message

This patch just modifies the "usage" word to "Usage" which enhances readability. Below is the patch Regards Alangi Derick Ndimnain diff --git a/git.c b/git.c index 42a4ee5..481aa74 100644 --- a/git.c +++ b/git.c @@ -667,7 +667,7 @@ int main(int argc, char **av) } else { /* The user didn't spe